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

CVE-2023-54367: Rejected CVE Entry Status and Details

CVE-2023-54367 is a rejected CVE entry that is no longer considered a valid vulnerability. This article explains the rejection status, provides context about why CVEs are rejected, and what this means for researchers.

Updated:

CVE-2023-54367 Overview

CVE-2023-54367 is a rejected CVE identifier. The National Vulnerability Database (NVD) marks this entry as withdrawn and does not associate it with any vulnerability, product, or vendor. No technical details, affected software, or exploitation data exist for this identifier.

Rejected CVE IDs typically result from duplicate assignments, withdrawn requests by the CVE Numbering Authority (CNA), or determinations that the reported issue does not qualify as a security vulnerability. Security teams should disregard this identifier during vulnerability triage and reference the authoritative NVD record for confirmation.

Critical Impact

This CVE ID has been rejected and carries no security impact. No action is required.

Affected Products

  • Not Available

Discovery Timeline

  • 2026-08-11 - CVE record published to NVD as rejected
  • 2026-08-11 - Last updated in NVD database

Technical Details for CVE-2023-54367

Vulnerability Analysis

No technical analysis applies to CVE-2023-54367. The identifier has been rejected by the assigning CNA, and NVD provides no descriptive metadata, Common Weakness Enumeration (CWE) mapping, or Common Vulnerability Scoring System (CVSS) vector. The rejection indicates the identifier should not be used to reference a security issue.

Organizations encountering references to this CVE ID in third-party tooling, threat intelligence feeds, or vulnerability scanners should treat those references as stale or erroneous. Cross-check any alerts against the official NVD entry to confirm the rejected status.

Root Cause

No root cause exists because no vulnerability was validated under this identifier. CVE IDs are rejected when duplicates are identified, when the reported behavior is determined to be intended functionality, or when the requester withdraws the submission.

Attack Vector

No attack vector applies. The identifier does not describe an exploitable condition.

No verified proof-of-concept code exists for this identifier. See the NVD entry for CVE-2023-54367 for the authoritative record.

Detection Methods for CVE-2023-54367

Indicators of Compromise

  • No indicators of compromise exist because no vulnerability is associated with this rejected identifier.
  • Any threat intelligence referencing CVE-2023-54367 as active should be treated as inaccurate.

Detection Strategies

  • Filter rejected CVE identifiers out of vulnerability management dashboards to reduce analyst noise.
  • Validate scanner findings against the NVD to confirm whether a referenced CVE is active, rejected, or reserved.

Monitoring Recommendations

  • Configure vulnerability management tooling to automatically suppress alerts tied to rejected CVE records.
  • Review vendor and third-party feeds periodically for stale references to withdrawn identifiers.

How to Mitigate CVE-2023-54367

Immediate Actions Required

  • No remediation is required. The identifier has been rejected and does not describe a security issue.
  • Update internal tracking systems to reflect the rejected status and close any tickets opened against this CVE.

Patch Information

No patch is required or available. Vendors have not published advisories because no vulnerability is associated with CVE-2023-54367.

Workarounds

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.