CVE-2022-23967: Rejected Duplicate CVE Entry (Reserved)

CVE-2022-23967 Overview

CVE-2022-23967 is a rejected CVE candidate that should not be used. This CVE entry has been formally rejected by the CVE Program and all references have been removed to prevent accidental usage.

Critical Impact

This CVE ID is a duplicate of CVE-2019-15679 and should not be referenced. All users should reference CVE-2019-15679 instead.

Affected Products

• Not Applicable - CVE has been rejected

Discovery Timeline

• 2022-01-26 - CVE-2022-23967 published to NVD
• 2023-11-07 - Last updated in NVD database with rejection status

Technical Details for CVE-2022-23967

Vulnerability Analysis

This CVE candidate has been rejected by the CVE Numbering Authority. The rejection reason indicates that CVE-2022-23967 is a duplicate entry of CVE-2019-15679. When duplicate CVE entries are identified, one is typically rejected to maintain a single authoritative reference for each unique vulnerability.

All technical details, references, and descriptions have been intentionally removed from this CVE entry to prevent security practitioners and automated systems from accidentally referencing or tracking the wrong identifier.

Root Cause

The root cause of this CVE entry's rejection is administrative rather than technical. CVE-2022-23967 was identified as a duplicate of an existing vulnerability that was already assigned CVE-2019-15679. To maintain the integrity of the CVE system and prevent confusion in vulnerability tracking, duplicate entries are formally rejected.

Attack Vector

Since this CVE has been rejected, there is no applicable attack vector. For information about the actual vulnerability, please reference CVE-2019-15679.

Detection Methods for CVE-2022-23967

Indicators of Compromise

• No IOCs are associated with this rejected CVE
• Any detection rules referencing CVE-2022-23967 should be updated to reference CVE-2019-15679

Detection Strategies

• Update vulnerability scanners and security tools to reference CVE-2019-15679 instead
• Review any existing detection rules that may reference this rejected CVE ID
• Ensure vulnerability management databases are synchronized with current NVD data

Monitoring Recommendations

• No active monitoring is required for this rejected CVE entry
• Redirect monitoring efforts to CVE-2019-15679 for the actual vulnerability

How to Mitigate CVE-2022-23967

Immediate Actions Required

• Do not use CVE-2022-23967 in any vulnerability tracking or reporting
• Reference CVE-2019-15679 for all technical details and mitigation guidance
• Update any documentation or security advisories that may reference this rejected CVE

Patch Information

Since CVE-2022-23967 has been rejected, no patches are associated with this specific CVE ID. For patching information related to the underlying vulnerability, please consult the security advisories and vendor guidance associated with CVE-2019-15679.

Workarounds

• Update internal vulnerability databases to mark CVE-2022-23967 as rejected
• Migrate any references in security tooling from CVE-2022-23967 to CVE-2019-15679
• Review organizational security documentation and update CVE references accordingly