Pippo is a modestly scoped application with a focused vulnerability profile centered on its single product. The durable signal reflects data-handling and parsing weaknesses—deserialization of untrusted data, improper input validation, and XML-related issues including entity expansion and external entity reference flaws—which are characteristic of applications that ingest and process unvalidated external input. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Pippo over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-18349CRITICAL 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, a | Oct 23, 2018 | 9.8 | 64 | NO | YES |
CVE-2018-18628CRITICAL An issue was discovered in Pippo 1.11.0. The function SerializationSessionDataTranscoder.decode() calls ObjectInputStream.readObject() to deserialize a SessionData object without c | Oct 23, 2018 | 9.8 | 32 | NO | NO |
CVE-2018-20059CRITICAL jaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE. | Dec 11, 2018 | 9.8 | 31 | NO | NO |
CVE-2018-18240CRITICAL 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 mechanis | Oct 11, 2018 | 9.8 | 31 | NO | NO |
CVE-2019-5442HIGH 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, th | Jun 12, 2019 | 7.5 | 24 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Pippo.
Media articles that mention a CVE ID that affects a product developed by Pippo — matched by CVE ID, not by vendor name.