CVE-2017-1219
UnknownEPSS 2.08%
Last modified
CVE-2017-1219 is a vulnerability of currently unknown severity. IBM Tivoli Endpoint Manager is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. EPSS estimates a 2.08% chance of exploitation in the next 30 days.
Description
IBM Tivoli Endpoint Manager is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 123859.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Ibm | Bigfix Platform | 9.1 |
| Ibm | Bigfix Platform | 9.1.3 |
| Ibm | Bigfix Platform | 9.1.4 |
| Ibm | Bigfix Platform | 9.1.5 |
| Ibm | Bigfix Platform | 9.1.6 |
| Ibm | Bigfix Platform | 9.1.7 |
| Ibm | Bigfix Platform | 9.2 |
| Ibm | Bigfix Platform | 9.2.0 |
| Ibm | Bigfix Platform | 9.2.1 |
| Ibm | Bigfix Platform | 9.2.2 |
| Ibm | Bigfix Platform | 9.2.3 |
| Ibm | Bigfix Platform | 9.2.4 |
| Ibm | Bigfix Platform | 9.2.5 |
| Ibm | Bigfix Platform | 9.2.6 |
| Ibm | Bigfix Platform | 9.2.7 |
References
- http://www.ibm.com/support/docview.wss?uid=swg22006014Vendor Advisory
- https://exchange.xforce.ibmcloud.com/vulnerabilities/123859VDB Entry, Vendor Advisory
- http://www.ibm.com/support/docview.wss?uid=swg22006014Vendor Advisory
- https://exchange.xforce.ibmcloud.com/vulnerabilities/123859VDB Entry, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1219?
IBM Tivoli Endpoint Manager is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 123859.
How severe is CVE-2017-1219?
Severity scoring for CVE-2017-1219 is pending analysis. The EPSS model estimates a 2.08% probability of exploitation in the next 30 days.
How do I fix CVE-2017-1219?
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.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-12184xorg-x11-server before 1.19.5 was missing length validation …
- CVE-2017-12185xorg-x11-server before 1.19.5 was missing length validation …
- CVE-2017-12186xorg-x11-server before 1.19.5 was missing length validation …
- CVE-2017-12187xorg-x11-server before 1.19.5 was missing length validation …
- CVE-2017-12188arch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when …7.8
- CVE-2017-12189It was discovered that the jboss init script as used in Red …
- CVE-2017-12190The bio_map_user_iov and bio_unmap_user functions in block/b…
- CVE-2017-12191A flaw was found in the CloudForms account configuration whe…
- CVE-2017-12192The keyctl_read_key function in security/keys/keyctl.c in th…
- CVE-2017-12193The assoc_array_insert_into_terminal_node function in lib/as…
- CVE-2017-12194A flaw was found in the way spice-client processed certain m…
- CVE-2017-12195A flaw was found in all Openshift Enterprise versions using …6.5
Are you affected by CVE-2017-1219?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST