CVE-2017-10617
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe ifmap service that comes bundled with Contrail has an XML External Entity (XXE) vulnerability that may allow an attacker to retrieve sensitive system files. Affected releases are Juniper Networks Contrail 2.2 prior to 2.21.4; 3.0 prior to 3.0.3.4; 3.1 prior to 3.1.4.0; 3.2 prior to 3.2.5.0. CVE-2017-10616 and CVE-2017-10617 can be chained together and have a combined CVSSv3 score of 5.8 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ifmap service bundled with Juniper Networks Contrail contains an XML External Entity (XXE) vulnerability that allows unauthenticated remote attackers to exploit insecure XML parsing and retrieve sensitive system files from the host. This occurs because the ifmap service processes XML without properly disabling external entity resolution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.2, < 2.21.4>= 3.0, < 3.0.3.4>= 3.1, < 3.1.4.0>= 3.2, < 3.2.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Contrail versionRun 'contrail-version' or check /etc/contrail/contrail-version.conf to obtain the installed Contrail versionAffected if version falls within >= 2.2 to < 2.21.4, >= 3.0 to < 3.0.3.4, >= 3.1 to < 3.1.4.0, or >= 3.2 to < 3.2.5.0
-
Verify ifmap service is presentCheck if the ifmap service is installed: look for ifmap binary via 'which ifmap' or check for ifmap process running via 'ps aux | grep ifmap'Affected if ifmap service is installed and running on the system
-
Confirm ifmap service is network-accessibleCheck if port 8443 (default ifmap port) is open and listening: run 'netstat -tlnp | grep 8443' or 'ss -tlnp | grep 8443'Affected if ifmap service is bound to a network interface and accessible from network
-
Review ifmap service configurationInspect /etc/contrail/ifmap.properties or similar configuration files to verify XML parsing settings for the ifmap serviceAffected if configuration does not explicitly disable external entity resolution in XML parsing
System is affected if Contrail version is within any of the vulnerable ranges AND the ifmap service is running and network-accessible, with XML parsing that allows external entity resolution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.21.43.0.3.43.1.4.0
Upgrade Contrail to the patched versions (2.21.4, 3.0.3.4, 3.1.4.0, or 3.2.5.0) which contain the fix for this XXE vulnerability. As a compensating control, network segmentation can limit exposure to the ifmap service.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10617 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data