CVE-2023-54375 Overview
CVE-2023-54375 is a rejected CVE identifier. The National Vulnerability Database (NVD) marks this entry as rejected because it was erroneously reserved under the wrong year by an automation defect. A correct-year CVE supersedes this identifier, and no vulnerability data is associated with CVE-2023-54375.
Critical Impact
No security impact. This CVE identifier is rejected and should not be used for tracking, scanning, or remediation workflows.
Affected Products
- No affected products listed
- No vendor information available
- No component data published
Discovery Timeline
- 2026-08-06 - CVE-2023-54375 published to NVD with rejected status
- 2026-08-06 - Last updated in NVD database
Technical Details for CVE-2023-54375
Vulnerability Analysis
CVE-2023-54375 does not describe a technical vulnerability. The NVD entry states the identifier was reserved in the wrong year due to an automation defect in the CVE assignment process. MITRE issued a rejection notice and directed downstream consumers to the correct-year CVE that supersedes this record.
Rejected CVEs remain in the catalog for auditability. Vulnerability management platforms preserve the identifier to avoid gaps in numbering but exclude it from scoring, scanning, and prioritization pipelines. Security teams encountering this ID in reports should confirm the superseding CVE identifier through the MITRE CVE List or NVD.
Root Cause
The root cause is administrative, not technical. An automation defect in the CVE reservation workflow assigned the identifier under an incorrect year. The record contains no CWE mapping, no CVSS vector, no affected product list, and no references beyond the rejection notice.
Attack Vector
No attack vector exists. The rejected CVE carries no exploitability characteristics because it does not describe a software or hardware flaw. No proof-of-concept code, exploit, or in-the-wild activity is associated with this identifier.
No code examples are applicable to a rejected CVE record.
Detection Methods for CVE-2023-54375
Indicators of Compromise
- No indicators of compromise apply to this identifier because no vulnerability is described.
- Any detection content or threat intelligence referencing CVE-2023-54375 should be reviewed and remapped to the correct-year CVE that supersedes it.
Detection Strategies
- Filter rejected CVE identifiers from vulnerability management dashboards to prevent noise in remediation queues.
- Cross-reference any tooling output that surfaces CVE-2023-54375 against the current MITRE CVE List to locate the superseding record.
Monitoring Recommendations
- Configure vulnerability scanners and SIEM correlation rules to suppress alerts tied to rejected CVE identifiers.
- Audit third-party threat feeds for stale references to CVE-2023-54375 and update ingestion logic to follow rejection pointers.
How to Mitigate CVE-2023-54375
Immediate Actions Required
- Remove CVE-2023-54375 from active tracking, ticketing, and reporting because the identifier is rejected.
- Identify the superseding correct-year CVE through NVD or the MITRE CVE List and apply mitigation guidance from that record instead.
Patch Information
No patch exists for CVE-2023-54375 because it does not describe a vulnerability. Consult the superseding CVE identifier for vendor advisories and fixed versions.
Workarounds
- No workarounds are required for this rejected identifier.
- Update internal documentation and detection content to reference the superseding CVE rather than CVE-2023-54375.
# No configuration changes apply to a rejected CVE identifier
# Query NVD for the superseding record:
# curl -s "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2023-54375"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
