|
12 | 12 | For further details, please see:
|
13 | 13 | https://nvd.nist.gov/vuln/detail/CVE-2019-17571,
|
14 | 14 | ESAPI GitHub Issue #538 (https://github.com/ESAPI/esapi-java-legacy/issues/538),
|
15 |
| - and the ESAPI security bulletin, "documentation/ESAPI-security-bulletin2.pdf", which |
| 15 | + and the ESAPI security advisory #2, "documentation/ESAPI-security-bulletin2.pdf", which |
16 | 16 | provides a detailed analysis of this issue in ESAPI.
|
17 | 17 | ]]></notes>
|
18 | 18 | <gav regex="true">^log4j:log4j:1\.2\.17$</gav>
|
19 | 19 | <cpe>cpe:/a:apache:log4j</cpe>
|
20 | 20 | <cve>CVE-2019-17571</cve>
|
21 | 21 | </suppress>
|
| 22 | + <suppress> |
| 23 | + <notes><![CDATA[ |
| 24 | + This suppresses CVE-2020-9488 for the log4j-1.2.17.jar dependency. ESAPI does |
| 25 | + not use it in a manner that makes it exploitable and ESAPI is unable to |
| 26 | + eliminate the dependency completely because our our deprecation policy. That specific |
| 27 | + CVE is the Java deserialization CVE reported in Log4J 1's SocketServer class which ESAPI |
| 28 | + doesn't use. |
| 29 | +
|
| 30 | + For further details, please see: |
| 31 | + https://nvd.nist.gov/vuln/detail/CVE-2020-9488, |
| 32 | + ESAPI GitHub Issue #534 (https://github.com/ESAPI/esapi-java-legacy/issues/534), |
| 33 | + and the ESAPI security advisory #4, "documentation/ESAPI-security-bulletin4.pdf", which |
| 34 | + provides a detailed analysis of this issue in ESAPI. |
| 35 | + ]]></notes> |
| 36 | + <gav regex="true">^log4j:log4j:1\.2\.17$</gav> |
| 37 | + <cpe>cpe:/a:apache:log4j</cpe> |
| 38 | + <cve>CVE-2020-9488</cve> |
| 39 | + </suppress> |
22 | 40 | </suppressions>
|
0 commit comments