netbird/advisory-database
0
0
Fork 0
mirror of https://github.com/netbirdio/advisory-database.git synced 2026-05-22 18:04:22 -07:00
Code Issues Packages Projects Releases Wiki Activity

Publish Advisories

Browse Source 
GHSA-4vc4-m8qh-g8jm
GHSA-96v5-c2h5-56hm
GHSA-gfh6-3pqw-x2j4
GHSA-96v5-c2h5-56hm
This commit is contained in:
advisory-database[bot]
2025-03-12 20:20:54 +00:00
parent 398c432149
commit 5ea969ca86
4 changed files with 229 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files
advisories/github-reviewed/2025/03/GHSA-4vc4-m8qh-g8jm/GHSA-4vc4-m8qh-g8jm.json
+81
View File
@@ -0,0 +1,81 @@
{
"schema_version": "1.4.0",
"id": "GHSA-4vc4-m8qh-g8jm",
"modified": "2025-03-12T20:20:25Z",
"published": "2025-03-12T20:20:24Z",
"aliases": [
"CVE-2025-25291"
],
"summary": "Ruby SAML allows a SAML authentication bypass due to DOCTYPE handling (parser differential)",
"details": "### Summary\nAn authentication bypass vulnerability was found in ruby-saml due to a parser differential.\nReXML and Nokogiri parse XML differently, the parsers can generate entirely different document structures from the same XML input. That allows an attacker to be able to execute a Signature Wrapping attack.\n\n### Impact\nThis issue may lead to authentication bypass.",
"severity": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U"
}
],
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "ruby-saml"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.12.4"
}
]
}
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "ruby-saml"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "1.13.0"
},
{
"fixed": "1.18.0"
}
]
}
]
}
],
"references": [
{
"type": "WEB",
"url": "https://github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-4vc4-m8qh-g8jm"
},
{
"type": "WEB",
"url": "https://github.com/SAML-Toolkits/ruby-saml/commit/e9c1cdbd0f9afa467b585de279db0cbd0fb8ae97"
},
{
"type": "PACKAGE",
"url": "https://github.com/SAML-Toolkits/ruby-saml"
}
],
"database_specific": {
"cwe_ids": [
"CWE-347",
"CWE-436"
],
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2025-03-12T20:20:24Z",
"nvd_published_at": null
}
}
advisories/github-reviewed/2025/03/GHSA-96v5-c2h5-56hm/GHSA-96v5-c2h5-56hm.json
+115
View File
@@ -0,0 +1,115 @@
{
"schema_version": "1.4.0",
"id": "GHSA-96v5-c2h5-56hm",
"modified": "2025-03-12T20:19:33Z",
"published": "2025-03-12T15:32:06Z",
"aliases": [
"CVE-2025-29891"
],
"summary": "Apache Camel Message Header Injection through request parameters",
"details": "Bypass/Injection vulnerability in Apache Camel.\n\nThis issue affects Apache Camel: from 4.9.0 before 4.10.2, from 4.0.0 before 4.8.5, from 3.10.0 before 3.22.4.\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 present in Camel's default incoming header filter, that allows an attacker to include Camel specific headers that for some Camel components can alter the behaviours such as the camel-bean component, or the camel-exec component.\n\nIf you have Camel applications that are directly connected to the internet via HTTP, then an attacker could include parameters in the HTTP requests that are sent to the Camel application that incorrectly get translated into headers. \n\nThe headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation.\n\nAll the known Camel HTTP component such as camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http would be vulnerable out of the box.\n\nThis CVE is related to the CVE-2025-27636: while they have the same root cause and are fixed with the same fix, CVE-2025-27636 was assumed to only be exploitable if an attacker could add malicious HTTP headers, while we have now determined that it is also exploitable via HTTP parameters. Like in CVE-2025-27636, exploitation is only possible if the Camel route uses particular vulnerable components.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L"
}
],
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.camel:camel-support"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.10.0"
},
{
"fixed": "3.22.4"
}
]
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.camel:camel-support"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.9.0"
},
{
"fixed": "4.10.2"
}
]
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.camel:camel-support"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.0.0-M1"
},
{
"fixed": "4.8.5"
}
]
}
]
}
],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-29891"
},
{
"type": "WEB",
"url": "https://github.com/apache/camel/commit/23a833eec6131a3cdce6e4b1b40b3ac2035b6adf"
},
{
"type": "WEB",
"url": "https://github.com/apache/camel/commit/45a6b74f7f8af8fd58f197566938a9534392a624"
},
{
"type": "WEB",
"url": "https://camel.apache.org/security/CVE-2025-27636.html"
},
{
"type": "WEB",
"url": "https://camel.apache.org/security/CVE-2025-29891.html"
},
{
"type": "PACKAGE",
"url": "https://github.com/apache/camel"
},
{
"type": "WEB",
"url": "https://issues.apache.org/jira/browse/CAMEL-21828"
}
],
"database_specific": {
"cwe_ids": [
"CWE-164"
],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2025-03-12T20:19:10Z",
"nvd_published_at": "2025-03-12T15:15:40Z"
}
}
advisories/unreviewed/2025/03/GHSA-gfh6-3pqw-x2j4/GHSA-gfh6-3pqw-x2j4.json → advisories/github-reviewed/2025/03/GHSA-gfh6-3pqw-x2j4/GHSA-gfh6-3pqw-x2j4.json
+33 -4
View File
@@ -1,11 +1,12 @@
{
"schema_version": "1.4.0",
"id": "GHSA-gfh6-3pqw-x2j4",
"modified": "2025-03-12T15:32:06Z",
"modified": "2025-03-12T20:19:58Z",
"published": "2025-03-12T15:32:06Z",
"aliases": [
"CVE-2025-2240"
],
"summary": "SmallRye Fault Tolerance out-of-memory (OOM) issue",
"details": "A flaw was found in Smallrye, where smallrye-fault-tolerance is vulnerable to an out-of-memory (OOM) issue. This vulnerability is externally triggered when calling the metrics URI. Every call creates a new object within meterMap and may lead to a denial of service (DoS) issue.",
"severity": [
{
@@ -13,12 +14,36 @@
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [],
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "io.smallrye:smallrye-fault-tolerance-core"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.9.0"
}
]
}
]
}
],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-2240"
},
{
"type": "WEB",
"url": "https://github.com/smallrye/smallrye-fault-tolerance/commit/e8bcad3d5e8bbac0a3219bd5c13661adf6ed6bbb"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2025-2240"
@@ -26,6 +51,10 @@
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2351452"
},
{
"type": "PACKAGE",
"url": "https://github.com/smallrye/smallrye-fault-tolerance"
}
],
"database_specific": {
@@ -33,8 +62,8 @@
"CWE-1325"
],
"severity": "HIGH",
"github_reviewed": false,
"github_reviewed_at": null,
"github_reviewed": true,
"github_reviewed_at": "2025-03-12T20:19:58Z",
"nvd_published_at": "2025-03-12T15:15:42Z"
}
}
advisories/unreviewed/2025/03/GHSA-96v5-c2h5-56hm/GHSA-96v5-c2h5-56hm.json
-40
View File
@@ -1,40 +0,0 @@
{
"schema_version": "1.4.0",
"id": "GHSA-96v5-c2h5-56hm",
"modified": "2025-03-12T18:32:52Z",
"published": "2025-03-12T15:32:06Z",
"aliases": [
"CVE-2025-29891"
],
"details": "Bypass/Injection vulnerability in Apache Camel.\n\nThis issue affects Apache Camel: from 4.10.0 before 4.10.2, from 4.8.0 before 4.8.5, from 3.10.0 before 3.22.4.\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 present in Camel's default incoming header filter, that allows an attacker to include Camel specific headers that for some Camel components can alter the behaviours such as the camel-bean component, or the camel-exec component.\n\nIf you have Camel applications that are directly connected to the internet via HTTP, then an attacker could include parameters in the HTTP requests that are sent to the Camel application that incorrectly get translated into headers. \n\nThe headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation.\n\nAll the known Camel HTTP component such as camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http would be vulnerable out of the box.\n\nThis CVE is related to the CVE-2025-27636: while they have the same root cause and are fixed with the same fix, CVE-2025-27636 was assumed to only be exploitable if an attacker could add malicious HTTP headers, while we have now determined that it is also exploitable via HTTP parameters. Like in CVE-2025-27636, exploitation is only possible if the Camel route uses particular vulnerable components.",
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L"
}
],
"affected": [],
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-29891"
},
{
"type": "WEB",
"url": "https://camel.apache.org/security/CVE-2025-27636.html"
},
{
"type": "WEB",
"url": "https://camel.apache.org/security/CVE-2025-29891.html"
}
],
"database_specific": {
"cwe_ids": [
"CWE-164"
],
"severity": "MODERATE",
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-12T15:15:40Z"
}
}