Deserialization in Pippo
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.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.055 (92.5th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 93rd percentile — 92.5% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.055 · newest: 0.055 · change: 0.000
Affected products
- Pippo — versions 1.11.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/pippo-java/pippo/issues/458 (Exploit, Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2018-18628?
- CVE-2018-18628 is a critical-severity vulnerability in Pippo, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2018-10-23.
- How severe is CVE-2018-18628?
- Critical severity. CVSS v3 base score is 9.8 out of 10.
- Is CVE-2018-18628 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.