CVE-2017-18349

Name: CVE-2017-18349
Creator: NVD / NIST
Published: 2018-10-23T20:29:00.263+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 38.97%

Last modified Jun 17, 2026

CVE-2017-18349 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 38.97% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability

38.97%

98.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-20

Affected Software

Vendor	Product	Versions
Alibaba	Fastjson	< 1.2.25
Pippo	Pippo	1.11.0

References

https://fortiguard.com/encyclopedia/ips/44059Mitigation, Third Party Advisory
https://github.com/alibaba/fastjson/wiki/security_update_20170315Mitigation, Third Party Advisory
https://github.com/pippo-java/pippo/issues/466Exploit, Third Party Advisory
https://fortiguard.com/encyclopedia/ips/44059Mitigation, Third Party Advisory
https://github.com/alibaba/fastjson/wiki/security_update_20170315Mitigation, Third Party Advisory
https://github.com/pippo-java/pippo/issues/466Exploit, Third Party Advisory

Timeline

Published: Oct 23, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-18349?

How severe is CVE-2017-18349?

Severity scoring for CVE-2017-18349 is pending analysis. The EPSS model estimates a 38.97% probability of exploitation in the next 30 days.

How do I fix CVE-2017-18349?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-18349?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST