What is CVE-2017-20151?

CVE-2017-20151 is a critical-severity XML external entity injection (XXE) vulnerability in com.itextpdf:itext-rups (maven), affecting versions <= 7.0.1. No fixed version is listed yet. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.

How severe is CVE-2017-20151?

CVE-2017-20151 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.itextpdf:itext-rups are affected by CVE-2017-20151?

com.itextpdf:itext-rups (maven) versions <= 7.0.1 is affected.

Is there a fix for CVE-2017-20151?

No fixed version is listed for CVE-2017-20151 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2017-20151 exploitable, and should I be worried?

Whether CVE-2017-20151 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-20151 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-20151 in com.itextpdf:itext-rups

Q: How severe is CVE-2017-20151?

CVE-2017-20151 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.itextpdf:itext-rups are affected by CVE-2017-20151?

com.itextpdf:itext-rups (maven) versions <= 7.0.1 is affected.

Q: Is there a fix for CVE-2017-20151?

No fixed version is listed for CVE-2017-20151 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2017-20151 exploitable, and should I be worried?

Whether CVE-2017-20151 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-20151 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-20151?

No fixed version is listed yet. In the interim: Disable external entity and DTD processing in your XML parser configuration.

Summary

iText RUPS XML External Entity vulnerability

A vulnerability classified as problematic was found in iText RUPS. This vulnerability affects unknown code of the file src/main/java/com/itextpdf/rups/model/XfaFile.java. The manipulation leads to xml external entity reference. The name of the patch is ac5590925874ef810018a6b60fec216eee54fb32. It is recommended to apply a patch to fix this issue. VDB-217054 is the identifier assigned to this vulnerability.

Impact

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

CVE-2017-20151 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

com.itextpdf:itext-rups (<= 7.0.1)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for CVE-2017-20151 yet.

In the interim: Disable external entity and DTD processing in your XML parser configuration.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-20151? CVE-2017-20151 is a critical-severity XML external entity injection (XXE) vulnerability in com.itextpdf:itext-rups (maven), affecting versions <= 7.0.1. No fixed version is listed yet. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
How severe is CVE-2017-20151? CVE-2017-20151 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.itextpdf:itext-rups are affected by CVE-2017-20151? com.itextpdf:itext-rups (maven) versions <= 7.0.1 is affected.
Is there a fix for CVE-2017-20151? No fixed version is listed for CVE-2017-20151 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2017-20151 exploitable, and should I be worried? Whether CVE-2017-20151 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-20151 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-20151? No fixed version is listed yet. In the interim: Disable external entity and DTD processing in your XML parser configuration.