Aggregates CVE and security vulnerability intelligence across all pippo-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Disclosed issues often relate to vendor risk xxe and vendor risk input validation; exposure may include vendor impact unexpected behavior in vendor surface production workloads and vendor surface software deployment contexts.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2019-5442 | XML Entity Expansion (Billion Laughs Attack) on Pippo 1.12.0 results in Denial of Service.Entities are created recursively and large amounts of heap memory is taken. Eventually, the JVM process will run out of memory. Otherwise, if the OS does not bound the memory on that process, memory will continue to be exhausted and will affect other processes on the system. | [email protected] | 7.5 | 0.33% | 2019-06-12 | 2024-11-21 |
| CVE-2018-20059 | jaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE. | [email protected] | 9.8 | 0.40% | 2018-12-11 | 2024-11-21 |
| CVE-2018-18628 | An issue was discovered in Pippo 1.11.0. The function SerializationSessionDataTranscoder.decode() calls ObjectInputStream.readObject() to deserialize a SessionData object without checking the object types. An attacker can create a malicious object, base64 encode it, and place it in the PIPPO_SESSION field of a cookie. Sending this cookie may lead to remote code execution. | [email protected] | 9.8 | 4.17% | 2018-10-23 | 2024-11-21 |
| CVE-2017-18349 | parseObject in Fastjson before 1.2.25, as used in FastjsonEngine in Pippo 1.11.0 and other products, allows remote attackers to execute arbitrary code via a crafted JSON request, as demonstrated by a crafted rmi:// URI in the dataSourceName field of HTTP POST data to the Pippo /json URI, which is mishandled in AjaxApplication.java. | [email protected] | 9.8 | 88.69% | 2018-10-23 | 2024-11-21 |
| CVE-2018-18240 | Pippo through 1.11.0 allows remote code execution via a command to java.lang.ProcessBuilder because the XstreamEngine component does not use XStream's available protection mechanisms to restrict unmarshalling. | [email protected] | 9.8 | 2.57% | 2018-10-11 | 2024-11-21 |