CVE-2017-18349

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 39%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
98.4%
KEV
Not listed

Published

October 23, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

lead to RCE when parse JSON string with Fastjson · Issue #466 · pippo-java/pippo · GitHub

https://github.com/pippo-java/pippo/issues/466
generic

security_update_20170315 · alibaba/fastjson Wiki · GitHub

https://github.com/alibaba/fastjson/wiki/security_update_20170315
generic

Just a moment

https://fortiguard.com/encyclopedia/ips/44059

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
com.alibaba:fastjson1.1.15 ... 1.2.9 (161 versions)1.2.31—
ro.pippo:pippo-fastjson0.10.0 ... 1.9.0 (23 versions)1.12.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 16:24 UTCEPSS rescore
  6. 2026-07-04 06:28 UTCEPSS rescore
  7. 2026-07-03 22:56 UTCOSV refresh
  8. 2026-07-02 16:54 UTCEPSS rescore
  9. 2026-07-01 15:02 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-30 23:19 UTCEPSS rescore
  12. 2026-06-29 14:03 UTCEPSS rescore
  13. 2026-06-28 14:04 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-27 03:06 UTCEPSS rescore
  16. 2026-06-27 03:05 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-19 19:23 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 17 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-16 17:50 UTCEPSS rescore
  4. 2026-06-15 17:45 UTCEPSS rescore
  5. 2026-06-15 11:13 UTCOSV refresh
  6. 2026-06-13 22:57 UTCEPSS rescore
  7. 2026-06-12 23:09 UTCEPSS rescore
  8. 2026-06-10 22:15 UTCEPSS rescore
  9. 2026-06-07 15:22 UTCEPSS rescore
  10. 2026-06-07 15:22 UTCEPSS rescore
  11. 2026-06-05 22:44 UTCEPSS rescore
  12. 2026-06-04 13:10 UTCEPSS rescore
  13. 2026-06-01 13:49 UTCEPSS rescore
  14. 2026-05-28 01:44 UTCEG score recompute
  15. 2026-05-27 13:38 UTCEPSS rescore
  16. 2026-05-27 13:38 UTCEPSS rescore
  17. 2026-05-26 23:13 UTCOSV refresh

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCh0cksr/Fastjson--CVE-2017-18349-
    First seen Apr 14, 2022
    Open source ↗
  • Nucleihttp/cves/2017/CVE-2017-18349.yaml
    First seen Jan 1, 2017

    Fastjson Insecure Deserialization - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-18349?
CVE-2017-18349 is a critical vulnerability published on October 23, 2018. 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…
When was CVE-2017-18349 disclosed?
CVE-2017-18349 was first published in the National Vulnerability Database on October 23, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-18349 actively exploited?
CVE-2017-18349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-18349?
CVE-2017-18349 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-18349?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18349, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-18349

Explore →

Is Your Infrastructure Affected by CVE-2017-18349?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs