CVE-2023-52892

Exp

In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.

Published: 2024-06-27 Last update: 2025-10-22 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-52892 is rated Exploit Available (59.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.18%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-52892

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-52892

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-16 0.14% 0.18% +0.05%
2 2025-08-06 0.28% 0.14% -0.14%
3 2025-08-05 — 0.28% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-52892

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-52892

GitHub Security Advisory for CVE-2023-52892

GHSA-ff7q-6vwh-v9m4 · Severity: high · Ecosystem: composer — Name confusion in x509 Subject Alternative Name fields

OS Trackers for CVE-2023-52892

vendor priority summary link
debian not yet assigned CVE-2023-52892 not yet assigned priority: Debian including 3 source packages (php-phpseclib, php-phpseclib3, phpseclib), 13 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 12, open 1. https://security-tracker.debian.org/tracker/CVE-2023-52892
ubuntu medium CVE-2023-52892 medium priority: Ubuntu including 3 source packages (php-phpseclib, php-phpseclib3, phpseclib), 28 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream, xenial): not-affected 12, released 12, ignored 3, DNE 1. https://ubuntu.com/security/CVE-2023-52892

Affected software / configurations for CVE-2023-52892

Vendor Product Version Raw CPE
phpseclib phpseclib >= 1.0.0, < 1.0.22 cpe:2.3:a:phpseclib:phpseclib:*:*:*:*:*:*:*:*
phpseclib phpseclib >= 2.0.0, < 2.0.46 cpe:2.3:a:phpseclib:phpseclib:*:*:*:*:*:*:*:*
phpseclib phpseclib >= 3.0.0, < 3.0.33 cpe:2.3:a:phpseclib:phpseclib:*:*:*:*:*:*:*:*

References for CVE-2023-52892

cvelogic Threat Intelligence