CVE-2022-36408 Overview
CVE-2022-36408 is a rejected CVE candidate that should not be used. This CVE entry was rejected because it is a duplicate of CVE-2022-31181, resulting from a typo that caused the wrong identifier to be assigned.
Important Notice
This CVE has been rejected and should not be referenced. All users should reference CVE-2022-31181 instead of this candidate.
Affected Products
- No affected products - This CVE has been rejected
Discovery Timeline
- 2022-07-22 - CVE-2022-36408 published to NVD
- 2023-11-07 - Last updated in NVD database with rejection status
Technical Details for CVE-2022-36408
Vulnerability Analysis
This CVE candidate has been formally rejected by the CVE Program. The rejection occurred because CVE-2022-36408 was erroneously created as a duplicate of CVE-2022-31181 due to a typographical error during the CVE assignment process. As a result, all technical references and vulnerability descriptions have been removed from this entry to prevent accidental usage.
Organizations that may have referenced CVE-2022-36408 in their vulnerability management systems, security documentation, or compliance reports should update their records to reference CVE-2022-31181 instead.
Root Cause
The root cause of this CVE rejection is administrative in nature—a typo during the CVE identification assignment process led to the creation of a duplicate entry. This is not a technical vulnerability root cause, as the CVE itself contains no valid vulnerability information.
Attack Vector
Not applicable. This CVE has been rejected and contains no vulnerability information. Users seeking technical details about the actual vulnerability should consult CVE-2022-31181.
Detection Methods for CVE-2022-36408
Indicators of Compromise
- No IOCs are associated with this rejected CVE
- Organizations should review any references to CVE-2022-36408 in their systems
- Check if vulnerability scanners have flagged this CVE and update to reference CVE-2022-31181
Detection Strategies
- Search internal documentation and vulnerability databases for references to CVE-2022-36408
- Review security tooling configurations that may reference this rejected CVE
- Audit compliance reports and risk assessments for incorrect CVE references
Monitoring Recommendations
- Update vulnerability management platforms to suppress or redirect CVE-2022-36408 findings
- Configure security tools to map CVE-2022-36408 to CVE-2022-31181 where possible
- Monitor vendor advisories that may have originally referenced this CVE for corrections
How to Mitigate CVE-2022-36408
Immediate Actions Required
- Replace all references to CVE-2022-36408 with CVE-2022-31181 in your vulnerability tracking systems
- Review and update any security documentation that references this rejected CVE
- Consult CVE-2022-31181 for actual vulnerability information and mitigation guidance
Patch Information
No patch information is available for CVE-2022-36408 as this CVE has been rejected. For patch information related to the actual vulnerability, please reference CVE-2022-31181 and consult the relevant vendor security advisories.
Workarounds
- Update vulnerability scanners and management tools to reference CVE-2022-31181
- Remove CVE-2022-36408 from any active vulnerability tracking lists
- Follow mitigation guidance provided under CVE-2022-31181 for the actual vulnerability
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


