PatchTheCVEcmdb vulnerabilities and fixes
Recent CVEs affecting cmdb, with upgrade or downgrade steps. 5 tracked.
cmdb has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 5. Most recent: 2023-04-16. Highest priority: CVE-2022-34125 (score 51/100).
- CVE-2022-34125 MEDIUM 6.5 UPGRADE front/icon.send.php in the CMDB plugin before 3.0.3 for GLPI allows attackers to gain read access to sensitive
- CVE-2022-1410 HIGH 8.0 UPGRADE OS Command Injection vulnerability in the db_optimize component of Device42 Asset Management Appliance allows
- CVE-2022-1401 MEDIUM 6.9 UPGRADE Improper Access Control vulnerability in the /Exago/WrImageResource.adx route as used in Device42 Asset Manage
- CVE-2022-1400 HIGH 7.1 UPGRADE Use of Hard-coded Cryptographic Key vulnerability in the WebReportsApi.dll of Exago Web Reports, as used in th
- CVE-2022-1399 CRITICAL 9.1 UPGRADE An Argument Injection or Modification vulnerability in the "Change Secret" username field as used in the Disco
FAQ
How do I fix cmdb vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is cmdb being exploited right now?
None of the tracked cmdb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which cmdb CVE should I patch first?
CVE-2022-34125 currently ranks highest (51/100): front/icon.send.php in the CMDB plugin before 3.0.3 for GLPI allows attackers to gain read access to sensitive.