Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.90% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-30171High confidence
An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78
Unknown · Unknown
5.9MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Debian Security Tracker: 1 affected package state with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.80-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | bouncycastle | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.80-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | bouncycastle | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.80-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | bouncycastle | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1.77-1ubuntu0.1~esm1 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges10 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.bouncycastle:bcprov-jdk14 | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bcprov-jdk15on | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bcprov-jdk15to18 | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bcprov-jdk18on | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bctls-fips | ECOSYSTEM: introduced 0; fixed 1.0.19 | 1.0.19 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bctls-jdk14 | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bctls-jdk15to18 | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.bouncycastle:bctls-jdk18on | ECOSYSTEM: introduced 0; fixed 1.78 | 1.78 | OSV record ↗aggregator derived · 10 Sep 2026 |
| NuGetBouncyCastle | ECOSYSTEM: introduced 0 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| NuGetBouncyCastle.Cryptography | ECOSYSTEM: introduced 0; fixed 2.3.1 | 2.3.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2024-30171 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybc-java: BouncyCastle vulnerable to a timing variant of Bleichenbacher (Marvin Attack)
The vendor explicitly identifies these products as affected by this CVE.
- org.bouncycastle-bcprov-jdk18on as a component of Cryostat 2
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat build of Apache Camel for Spring Boot 3
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat Build of Keycloak
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat Fuse 7
- Summary
- A flaw was found in the Bouncy Castle Java cryptography APIs. Affected versions of the org.bouncycastle:bcprov-jdk18on package are vulnerable to Observable Timing Discrepancy via the PKCS#1 1.5 and OAEP decryption process (a.k.a. Marvin Attack). An attacker can recover cipher-texts via a side-channel attack by exploiting the Marvin security flaw. The PKCS#1 1.5 attack vector leaks data via javax.crypto.Cipher exceptions and the OAEP interface vector leaks via the bit size of the decrypted data.
- Remediation
- Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
SSA-485750 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-485750: Multiple Vulnerabilities in SIDIS Prime Before V4.0.800
The vendor explicitly identifies these products as affected by this CVE.
- SIDIS Prime
- Summary
- An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing.
- Remediation
- Update to V4.0.800 or later version
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing.
What
An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing.
Why
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing.
Why
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Observable Discrepancy → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-203 ↗
CWE-203: Observable Discrepancy. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- org.bouncycastle-bcprov-jdk18on as a component of Cryostat 2
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat build of Apache Camel for Spring Boot 3
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat Build of Keycloak
- org.bouncycastle-bcprov-jdk18on as a component of Red Hat Fuse 7
- Fixed
- eap7-bouncycastle-0:1.78.1-1.redhat_00002.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- eap7-bouncycastle-0:1.78.1-1.redhat_00002.1.el7eap.src as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- eap7-bouncycastle-mail-0:1.78.1-1.redhat_00002.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- eap7-bouncycastle-pg-0:1.78.1-1.redhat_00002.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- eap7-bouncycastle-pkix-0:1.78.1-1.redhat_00002.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- eap7-bouncycastle-prov-0:1.78.1-1.redhat_00002.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- eap7-bouncycastle-util-0:1.78.1-1.redhat_00002.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server
- cryostat-tech-preview/cryostat-db-rhel8@sha256:e3bdab63bdfa8f8bd586e35c3a3c8fe5dc6bbcb1a4a58286b61239f3b71c9da7_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-db-rhel8@sha256:f46e8d58e38cc7a89f30ad7d0cb9c216f107628c2913ccec2361c91f8f6a7f7f_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-grafana-dashboard-rhel8@sha256:31237230e7d52fd09434efff343043d8c1588eff15b5d99bcdf938a1b739613d_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-grafana-dashboard-rhel8@sha256:3679ad644998b29fe5f356b0dd7494ff3356a09ba8101fa41cfdf54ac0e7461d_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-operator-bundle@sha256:1787c8b5cff79d2fdd6f38bd4dfd4e7a7d3485dbb3493e134e9f344ab6b1354b_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-operator-bundle@sha256:ca41b2d1ce8de6065d452d11e81b648c7c52a5ebb99921f20a72218373c57206_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-ose-oauth-proxy-rhel8@sha256:4959f510d66b7960eb04125d4efb5aa179212049ef0778ebd10fbd5d11ce2786_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-ose-oauth-proxy-rhel8@sha256:52620ece35d7c05f9aa5ed9f97f76d2cad0a6eb6ffa61e26608919e24fcf8bb0_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-reports-rhel8@sha256:2d7c8bd9040222ce5a13403db92f8b323e268465ff17e5347c8f15ef976b356a_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-reports-rhel8@sha256:7803f76d816122212fb2e0f20d9ecbab29e4c287ffba7be3464b37ec06d51219_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-rhel8-operator@sha256:18b1cccd75118ad3e84467f048018353ad33437497b88a8d56154fdf0b010092_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-rhel8-operator@sha256:9a09c2579d683325936a3ee69129c156b09f2e7c05d0ed40ab01a30b365a2d18_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-rhel8@sha256:14b8f92b9e754d0dc6e107d88b52fddb5d5ca11d26e7d41178c9316c45ab29d9_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-rhel8@sha256:9593de391de6fbef67c3410e6b39066306b8047fb140079617ca3522a782ebb3_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-storage-rhel8@sha256:a63472e6434616e815f1cbd776c0bf5ee5a112d82312a61885cc4018a5695f81_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/cryostat-storage-rhel8@sha256:e38803c79654de50129cca99c94ab373c4b3f028601bf690deb8b96b3b32f7bb_arm64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/jfr-datasource-rhel8@sha256:41abaab9901edeab4b43ee8dc472fc58d67cf7a28dc61eaeee1192095fbee277_amd64 as a component of Cryostat 3 on RHEL 8
- cryostat-tech-preview/jfr-datasource-rhel8@sha256:b50ae0b0cb72db2bc9e24bec3f19933a3c8e8fb9148bc78b5b60e9f6cf37f13f_arm64 as a component of Cryostat 3 on RHEL 8
- eap7-bouncycastle-0:1.78.1-1.redhat_00002.1.el8eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 8
- eap7-bouncycastle-0:1.78.1-1.redhat_00002.1.el8eap.src as a component of Red Hat JBoss EAP 7.4 for RHEL 8
- eap7-bouncycastle-mail-0:1.78.1-1.redhat_00002.1.el8eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 8
- eap7-bouncycastle-pg-0:1.78.1-1.redhat_00002.1.el8eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 8
- eap7-bouncycastle-pkix-0:1.78.1-1.redhat_00002.1.el8eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 8
- and 263 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 9 May 2024 · Last source change 19 Aug 2024, 17:18 UTC · CWE-203 · Observable Discrepancy
CVE recordCVE.org · 5.1
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2024-1786
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD not scheduled
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- n/a · Fixed: Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.