Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2023-54372

CVE-2023-54372: Rejected CVE Vulnerability Entry

CVE-2023-54372 is a rejected CVE entry that has been removed from the official vulnerability database. This post explains the rejection status, common reasons for CVE rejections, and implications for researchers.

Published:

CVE-2023-54372 Overview

CVE-2023-54372 has been rejected by the CVE Numbering Authority. The identifier is no longer considered a valid vulnerability record and should not be referenced in vulnerability management workflows or risk assessments.

Rejected CVE identifiers typically indicate one of several conditions: the reported issue was determined not to be a security vulnerability, the identifier was a duplicate of another CVE, the reservation was withdrawn, or the submission did not meet CVE assignment criteria. No technical details, affected products, or exploitation information are associated with this identifier.

Critical Impact

No impact. This CVE ID has been rejected and carries no vulnerability data, CVSS score, or affected product listing.

Affected Products

  • No affected products listed
  • No vendor associated with this identifier
  • No component information available

Discovery Timeline

  • 2026-08-11 - CVE-2023-54372 published to NVD with rejected status
  • 2026-08-11 - Last updated in NVD database

Technical Details for CVE-2023-54372

Vulnerability Analysis

No technical vulnerability analysis is available for CVE-2023-54372. The CVE record carries a rejection notice from the CVE Numbering Authority, meaning the reserved identifier will not be populated with vulnerability data.

Security teams should remove this identifier from tracking systems, detection rules, and compliance reports. Referencing a rejected CVE in vulnerability management processes can create noise and false accountability in audit trails.

Root Cause

No root cause exists because no vulnerability was validated under this identifier. Rejection reasons are not disclosed in the NVD record beyond the standard rejection notice.

Attack Vector

No attack vector applies. The identifier carries no CVSS vector, no Common Weakness Enumeration mapping, and no proof-of-concept references.

Detection Methods for CVE-2023-54372

Indicators of Compromise

  • No indicators of compromise apply to this rejected CVE identifier.
  • Any detection content referencing CVE-2023-54372 should be reviewed and removed.

Detection Strategies

  • Audit vulnerability scanners and SIEM correlation rules for references to CVE-2023-54372 and retire them.
  • Confirm with upstream threat intelligence feeds that the rejected status has propagated to internal databases.

Monitoring Recommendations

  • Monitor the NVD feed for status changes to rejected identifiers, though re-activation is uncommon.
  • Track CVE list updates from MITRE to ensure vulnerability inventories reflect the current authoritative state.

How to Mitigate CVE-2023-54372

Immediate Actions Required

  • No patching or mitigation is required for a rejected CVE identifier.
  • Remove CVE-2023-54372 from active vulnerability tracking, ticketing systems, and executive risk dashboards.
  • Communicate the rejected status to stakeholders who may have received prior alerts referencing this ID.

Patch Information

No patches exist because no vulnerability was validated. Vendors have not issued advisories for CVE-2023-54372.

Workarounds

  • No workarounds are applicable to a rejected CVE.
  • Redirect vulnerability management effort to actively published CVEs affecting your environment.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.