atomicparsley vulnerabilities and fixes
Recent CVEs affecting atomicparsley, with upgrade or downgrade steps. 2 tracked.
atomicparsley has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2021-08-04. Highest priority: CVE-2021-37232 (score 65/100).
- CVE-2021-37232 CRITICAL 9.8 UPGRADE A stack overflow vulnerability occurs in Atomicparsley 20210124.204813.840499f through APar_read64() in src/ut
- CVE-2021-37231 MEDIUM 5.5 DOWNGRADE A stack-buffer-overflow occurs in Atomicparsley 20210124.204813.840499f through APar_readX() in src/util.cpp w
FAQ
How do I fix atomicparsley 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 atomicparsley being exploited right now?
None of the tracked atomicparsley CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which atomicparsley CVE should I patch first?
CVE-2021-37232 currently ranks highest (65/100): A stack overflow vulnerability occurs in Atomicparsley 20210124.204813.840499f through APar_read64() in src/ut.