diff --git a/advisories/github-reviewed/2025/01/GHSA-m3hp-8546-5qmr/GHSA-m3hp-8546-5qmr.json b/advisories/github-reviewed/2025/01/GHSA-m3hp-8546-5qmr/GHSA-m3hp-8546-5qmr.json index 38c3ac2fd15..c8047b4877c 100644 --- a/advisories/github-reviewed/2025/01/GHSA-m3hp-8546-5qmr/GHSA-m3hp-8546-5qmr.json +++ b/advisories/github-reviewed/2025/01/GHSA-m3hp-8546-5qmr/GHSA-m3hp-8546-5qmr.json @@ -1,13 +1,12 @@ { "schema_version": "1.4.0", "id": "GHSA-m3hp-8546-5qmr", - "modified": "2025-01-22T18:18:25Z", + "modified": "2025-03-10T21:07:03Z", "published": "2025-01-22T15:32:35Z", - "aliases": [ - "CVE-2025-0604" - ], - "summary": "Authentication Bypass Due to Missing LDAP Bind After Password Reset in Keycloak ", - "details": "A flaw was found in Keycloak. When an Active Directory user resets their password, the system updates it without performing an LDAP bind to validate the new credentials against AD. This vulnerability allows users whose AD accounts are expired or disabled to regain access in Keycloak, bypassing AD restrictions. The issue enables authentication bypass and could allow unauthorized access under certain conditions.", + "withdrawn": "2025-03-10T21:07:03Z", + "aliases": [], + "summary": "Duplicate Advisory: Authentication Bypass Due to Missing LDAP Bind After Password Reset in Keycloak ", + "details": "# Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-2p82-5wwr-43cw. This link is maintained to preserve external references.\n\n# Original Description\n\nA flaw was found in Keycloak. When an Active Directory user resets their password, the system updates it without performing an LDAP bind to validate the new credentials against AD. This vulnerability allows users whose AD accounts are expired or disabled to regain access in Keycloak, bypassing AD restrictions. The issue enables authentication bypass and could allow unauthorized access under certain conditions.", "severity": [ { "type": "CVSS_V3", @@ -40,6 +39,10 @@ "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0604" }, + { + "type": "WEB", + "url": "https://access.redhat.com/errata/RHSA-2025:2545" + }, { "type": "WEB", "url": "https://access.redhat.com/security/cve/CVE-2025-0604" diff --git a/advisories/github-reviewed/2025/03/GHSA-2c2h-2855-mf97/GHSA-2c2h-2855-mf97.json b/advisories/github-reviewed/2025/03/GHSA-2c2h-2855-mf97/GHSA-2c2h-2855-mf97.json index 437b88746e3..c3e196cea37 100644 --- a/advisories/github-reviewed/2025/03/GHSA-2c2h-2855-mf97/GHSA-2c2h-2855-mf97.json +++ b/advisories/github-reviewed/2025/03/GHSA-2c2h-2855-mf97/GHSA-2c2h-2855-mf97.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-2c2h-2855-mf97", - "modified": "2025-03-10T20:49:46Z", + "modified": "2025-03-10T21:06:44Z", "published": "2025-03-09T15:31:19Z", "aliases": [ "CVE-2025-27636" ], "summary": "Apache Camel: Camel Message Header Injection via Improper Filtering", - "details": "Bypass/Injection vulnerability in Apache Camel-Bean component under particular conditions.\n\nThis issue affects Apache Camel: from 4.9.0 through <= 4.10.1, from 4.2.0 through <= 4.8.4, from 3.10.0 through <= 3.22.3.\n\nUsers are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases.\n\nThis vulnerability is only present in the following situation. The user is using one of the following HTTP Servers via one the of the following Camel components\n\n * camel-servlet\n * camel-jetty\n * camel-undertow\n * camel-platform-http\n * camel-netty-http\n\n\nand in the route, the exchange will be routed to a camel-bean producer. So ONLY camel-bean component is affected. In particular: \n\n * The bean invocation (is only affected if you use any of the above together with camel-bean component).\n\n * The bean that can be called, has more than 1 method implemented.\nIn these conditions an attacker could be able to forge a Camel header name and make the bean component invoking other methods in the same bean.\n\nThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\". \n\n\nMitigation: You can easily work around this in your Camel applications by removing the headers in your Camel routes. There are many ways of doing this, also globally or per route. This means you could use the removeHeaders EIP, to filter out anything like \"cAmel, cAMEL\" etc, or in general everything not starting with \"Camel\", \"camel\" or \"org.apache.camel.\".", + "details": "Bypass/Injection vulnerability in Apache Camel-Bean component under particular conditions.\n\nThis issue affects Apache Camel: from 4.9.0 through <= 4.10.1, from 4.0.0-M1 through <= 4.8.4, from 3.10.0 through <= 3.22.3.\n\nUsers are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases.\n\nThis vulnerability is only present in the following situation. The user is using one of the following HTTP Servers via one the of the following Camel components\n\n * camel-servlet\n * camel-jetty\n * camel-undertow\n * camel-platform-http\n * camel-netty-http\n\n\nand in the route, the exchange will be routed to a camel-bean producer. So ONLY camel-bean component is affected. In particular: \n\n * The bean invocation (is only affected if you use any of the above together with camel-bean component).\n\n * The bean that can be called, has more than 1 method implemented.\nIn these conditions an attacker could be able to forge a Camel header name and make the bean component invoking other methods in the same bean.\n\nThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\". \n\n\nMitigation: You can easily work around this in your Camel applications by removing the headers in your Camel routes. There are many ways of doing this, also globally or per route. This means you could use the removeHeaders EIP, to filter out anything like \"cAmel, cAMEL\" etc, or in general everything not starting with \"Camel\", \"camel\" or \"org.apache.camel.\".", "severity": [ { "type": "CVSS_V4", @@ -44,7 +44,7 @@ "type": "ECOSYSTEM", "events": [ { - "introduced": "4.2.0" + "introduced": "4.0.0-M1" }, { "fixed": "4.8.5" @@ -86,10 +86,6 @@ "type": "WEB", "url": "https://github.com/apache/camel/commit/45a6b74f7f8af8fd58f197566938a9534392a624" }, - { - "type": "WEB", - "url": "https://github.com/apache/camel/commit/9b59f350f6bc6718145529426e8e2d2e5e15bc45" - }, { "type": "WEB", "url": "https://camel.apache.org/security/CVE-2025-27636.html" diff --git a/advisories/github-reviewed/2025/03/GHSA-2p82-5wwr-43cw/GHSA-2p82-5wwr-43cw.json b/advisories/github-reviewed/2025/03/GHSA-2p82-5wwr-43cw/GHSA-2p82-5wwr-43cw.json new file mode 100644 index 00000000000..ec8b69077f5 --- /dev/null +++ b/advisories/github-reviewed/2025/03/GHSA-2p82-5wwr-43cw/GHSA-2p82-5wwr-43cw.json @@ -0,0 +1,92 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-2p82-5wwr-43cw", + "modified": "2025-03-10T21:07:30Z", + "published": "2025-03-10T21:07:29Z", + "aliases": [ + "CVE-2025-0604" + ], + "summary": "Authentication Bypass Due to Missing LDAP Bind After Password Reset in Keycloak", + "details": "The issue arises because Keycloak does not perform an LDAP bind after a password reset, leading to potential authentication bypass for expired or disabled AD accounts. A fix should enforce LDAP validation after password updates to ensure consistency with AD authentication policies.", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "Maven", + "name": "org.keycloak:keycloak-ldap-federation" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "26.1.0" + }, + { + "fixed": "26.1.3" + } + ] + } + ] + }, + { + "package": { + "ecosystem": "Maven", + "name": "org.keycloak:keycloak-ldap-federation" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "26.0.10" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/keycloak/keycloak/security/advisories/GHSA-2p82-5wwr-43cw" + }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0604" + }, + { + "type": "WEB", + "url": "https://access.redhat.com/errata/RHSA-2025:2545" + }, + { + "type": "WEB", + "url": "https://access.redhat.com/security/cve/CVE-2025-0604" + }, + { + "type": "WEB", + "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2338993" + }, + { + "type": "PACKAGE", + "url": "https://github.com/keycloak/keycloak" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-287" + ], + "severity": "MODERATE", + "github_reviewed": true, + "github_reviewed_at": "2025-03-10T21:07:29Z", + "nvd_published_at": null + } +} \ No newline at end of file