CVE-2017-11427: Multiple SAML libraries may allow authentication bypass via incorrect XML canonicalization and DOM traversal
Noroxi assessment
Priority: Plan (action score 40/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.3% (FIRST EPSS); higher than 91.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: python-python3-saml (openSUSE:Tumbleweed) 1.15.0-2.3, 1.16.0-2.4; python-saml (PyPI) 2.4.0; python-defusedxml (SUSE:Enterprise Storage 6) 0.6.0-1.5.1.
- Severity is disputed: the assigning authority (CNA) scores it 7.7, NVD 9.8.
Add it to your regular patch cycle. Upgrade to python-python3-saml (openSUSE:Tumbleweed) 1.15.0-2.3, 1.16.0-2.4; python-saml (PyPI) 2.4.0; python-defusedxml (SUSE:Enterprise Storage 6) 0.6.0-1.5.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
OneLogin PythonSAML 2.3.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.
- Published
- Apr 17, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.3% · 91th percentile
- CWE
- CWE-287
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.3%
CNA vs NVD score
- NVD
- 9.8
- CNA · duo
- 7.7
- 2.1 point gap
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| onelogin | pythonsaml | cpe:2.3:a:onelogin:pythonsaml |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (duo). Independent of NVD's CPE analysis and usually ahead of it.
OneLogin PythonSAML
- unspecified and later · before 2.3.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- onelogin pythonsamlup to 2.3.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Tumbleweed | python-python3-saml | before 1.15.0-2.3 | 1.15.0-2.3 |
| openSUSE:Tumbleweed | python-python3-saml | before 1.16.0-2.4 | 1.16.0-2.4 |
| PyPI | python-saml | before 2.4.0 | 2.4.0 |
| SUSE:Enterprise Storage 6 | python-defusedxml | before 0.6.0-1.5.1 | 0.6.0-1.5.1 |
| SUSE:Enterprise Storage 6 | python-freezegun | before 0.3.12-1.5.1 | 0.3.12-1.5.1 |
| SUSE:Enterprise Storage 6 | python-isodate | before 0.6.0-1.3.2 | 0.6.0-1.3.2 |
| SUSE:Enterprise Storage 6 | python-pkgconfig | before 1.5.1-1.5.1 | 1.5.1-1.5.1 |
| SUSE:Enterprise Storage 6 | python-python3-saml | before 1.9.0-1.5.2 | 1.9.0-1.5.2 |
| SUSE:Enterprise Storage 6 | python-xmlsec | before 1.3.6-1.5.1 | 1.3.6-1.5.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:python-python3-saml | 1.15.0-2.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:python-saml | 2.4.0 | Package registry (OSV) |
| suse:python-defusedxml | 0.6.0-1.5.1 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
| suse:python-freezegun | 0.3.12-1.5.1 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
| suse:python-isodate | 0.6.0-1.3.2 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
| suse:python-pkgconfig | 1.5.1-1.5.1 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
| suse:python-python3-saml | 1.9.0-1.5.2 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
| suse:python-xmlsec | 1.3.6-1.5.1 · SUSE:Enterprise Storage 6 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:12 | 2018-03-03 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-410 d
- Published
- TodayNov 16, 2026+2770 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Kelby LudwigDuo Security
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.