Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GHSA-4h8f-2wvx-gg5w] Bouncy Castle Java Cryptography API vulnerable to DNS poisoning #5186

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,14 +1,16 @@
{
"schema_version": "1.4.0",
"id": "GHSA-4h8f-2wvx-gg5w",
"modified": "2024-06-14T15:31:24Z",
"modified": "2024-06-14T15:32:27Z",
"published": "2024-05-03T18:30:37Z",
"aliases": [
"CVE-2024-34447"
],
"summary": "Bouncy Castle Java Cryptography API vulnerable to DNS poisoning",
"details": "An issue was discovered in Bouncy Castle Java Cryptography APIs before BC 1.78. When endpoint identification is enabled in the BCJSSE and an SSL socket is created without an explicit hostname (as happens with HttpsURLConnection), hostname verification could be performed against a DNS-resolved IP address in some situations, opening up a possibility of DNS poisoning.",
"severity": [],
"severity": [

],
"affected": [
{
"package": {
Expand Down Expand Up @@ -67,25 +69,6 @@
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.bouncycastle:bcprov-jdk13"
},
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "1.61"
},
{
"fixed": "1.78"
}
]
}
]
},
{
"package": {
"ecosystem": "Maven",
Expand Down Expand Up @@ -133,7 +116,9 @@
}
],
"database_specific": {
"cwe_ids": [],
"cwe_ids": [

],
"severity": "LOW",
"github_reviewed": true,
"github_reviewed_at": "2024-05-03T20:34:32Z",
Expand Down
Loading