Security Resilience

CVE-2023-33201

Crypto Weakness in Bouncycastle Bc-Java ≤ 1.74

Published
05 July 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0077 56th percentile
Risk Priority 46 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-33201 is a medium-severity Improper Certificate Validation (CWE-295) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Masquerading (T1036); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Bouncy Castle For Java before 1.74 is affected by an LDAP injection vulnerability. The vulnerability only affects applications that use an LDAP CertStore from Bouncy Castle to validate X.509 certificates. During the certificate validation process, Bouncy Castle inserts the certificate's…

more

Subject Name into an LDAP search filter without any escaping, which leads to an LDAP injection vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1495 Firmware Corruption Impact
Adversaries may overwrite or corrupt the flash memory contents of system BIOS or other firmware in devices attached to a system in order to render them inoperable or unable to boot, thus denying the availability to use the devices and/or…
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-8763Same product: Bouncycastle Bc-Java
CVE-2026-58062Same product: Bouncycastle Bc-Java
CVE-2024-14041Same product: Bouncycastle Bc-Java
CVE-2026-17507Same product: Bouncycastle Bc-Java
CVE-2026-59652Same product: Bouncycastle Bc-Java
CVE-2026-59644Same product: Bouncycastle Bc-Java
CVE-2026-12852Same product: Bouncycastle Bc-Java
CVE-2026-103602Same vendor: Bouncycastle
CVE-2026-63576Same vendor: Bouncycastle
CVE-2026-63577Same vendor: Bouncycastle

Affected Assets

bouncycastle
bc-java
≤ 1.74

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 12 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-295

When certificates are used to establish component provenance, the control requires correct certificate validation procedures.

addresses: CWE-295

Mandates approved trust anchors and issuance policies, directly preventing acceptance of unvalidated or untrusted certificates.

addresses: CWE-295

Correct system time is required for proper enforcement of certificate notBefore/notAfter dates and time-based revocation checks.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.AA-03 mostly match
blocks

Certificate-based authentication of users/services/hardware directly depends on correct validation.

PR.DS-02 mostly match
blocks

Proper certificate validation is a core mechanism for protecting data-in-transit confidentiality and integrity.

PR.PS-06 mostly match
blocks

Secure development practices explicitly include implementing correct certificate validation logic.

ID.RA-09 partial match
blocks

Assessing authenticity/integrity of acquired software often relies on code-signing certificate validation.

PR.AA-04 partial match
blocks

Identity assertions conveyed via certificates require validation to be verified.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's programme (code review, static analysis, penetration testing) reaches most CWE-295 instances as first-party code defects — missing SSL_get_verify_result calls, disabled validation flags, unchecked hostname matching — all visible in source or observable at runtime by presenting an invalid certificate; the bounded remainder is instances where certificate pinning makes post-implementation testing difficult (noted in the CWE's Modes of Introduction) and validation logic buried inside third-party libraries that the developer's source-level review does not read, though pen-testing catches the symptom in many of those.

prevents

Training developers on proper TLS/certificate validation APIs and the importance of chain, hostname, and revocation checks reduces some instances of CWE-295, but the weakness is a specialized implementation defect where even trained developers make mistakes (e.g., skipping SSL_get_verify_result, accepting self-signed certs, using curl -k), so the effect is a minority one — consistent with the A.6.3 vs CWE-598 anchor at the same rung.

blocks

Requiring issuance and validation of public-key certificates under an approved policy reduces the chance that certificates with improper validation will be trusted.

prevents

A.8.28 mandates secure coding practices (standards, peer review, training, prohibition of insecure techniques) that reduce improper certificate validation defects, but the mechanism is human practice and is fallible; the clause's declared ceiling on this verb is `partial`, matching the same-clause grades against CWE-79 and CWE-502.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like improper certificate validation the way those practices do, at `partial` -- the same reasoning the owner applied to A.8.30 -> CWE-134, and the clause carries a declared ceiling of `partial` on this verb.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. CWE-295 does surface as CVEs (Apple goto fail, Go framework, router firmware, etc.), so the disclosed share is found, but the bulk of certificate-validation defects live in custom first-party code with no published advisory, which is outside A.8.8's reach and belongs to A.8.29.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (3 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-295
  • V-248531 OL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-295
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295

References