CVE-2017-18122: A signature-validation bypass issue was discovered in SimpleSAMLphp through 1.14.16.
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 66% 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. Special conditions such as timing or configuration are required.
- Fixed version: simplesamlphp (Debian:12) 1.15.0-1; simplesamlphp (Debian:7) 1.9.2-1+deb7u2; simplesamlphp (Debian:8) 1.13.1-2+deb8u1.
Low priority for now. Upgrade to simplesamlphp (Debian:12) 1.15.0-1; simplesamlphp (Debian:7) 1.9.2-1+deb7u2; simplesamlphp (Debian:8) 1.13.1-2+deb8u1 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
A signature-validation bypass issue was discovered in SimpleSAMLphp through 1.14.16. A SimpleSAMLphp Service Provider using SAML 1.1 will regard as valid any unsigned SAML response containing more than one signed assertion, provided that the signature of at least one of the assertions is valid. Attributes contained in all the assertions received will be merged and the entityID of the first assertion received will be used, allowing an attacker to impersonate any user of any IdP given an assertion signed by the targeted IdP.
- Published
- Feb 2, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 66th percentile
- CWE
- CWE-347
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- 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 |
|---|---|---|
| simplesamlphp | simplesamlphp | cpe:2.3:a:simplesamlphp:simplesamlphp |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux7.0
- debian debian linux8.0
- debian debian linux9.0
- simplesamlphp simplesamlphpup to 1.14.16 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | simplesamlphp | before 1.15.0-1 | 1.15.0-1 |
| Debian:7 | simplesamlphp | before 1.9.2-1+deb7u2 | 1.9.2-1+deb7u2 |
| Debian:8 | simplesamlphp | before 1.13.1-2+deb8u1 | 1.13.1-2+deb8u1 |
| Debian:9 | simplesamlphp | before 1.14.11-1+deb9u1 | 1.14.11-1+deb9u1 |
| Packagist | simplesamlphp/simplesamlphp | before 1.14.17 | 1.14.17 |
Same product
simplesamlphp: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-6521The sqlauth module in SimpleSAMLphp before 1.15.2 relies on the MySQL utf8 charset, which truncates queries upon encountering four-byte…40Plan
- CVE-2017-12868The secureCompare method in lib/SimpleSAML/Utils/Crypto.php in SimpleSAMLphp 1.14.13 and earlier, when used with PHP before 5.6, allows…40Plan
- CVE-2017-12873SimpleSAMLphp 1.7.0 through 1.14.10 might allow attackers to obtain sensitive information, gain unauthorized access, or have unspecified…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2018-6520Feb 1, 2018 · SimpleSAMLphp before 1.15.2 allows remote attackers to bypass an open redirect protection mechanism via crafted authority data in a URL.24Monitor
- ← EarlierCVE-2017-18121Feb 2, 2018 · The consentAdmin module in SimpleSAMLphp through 1.14.15 is vulnerable to a Cross-Site Scripting attack, allowing an attacker to craft…24Monitor
- Later →CVE-2018-7644Mar 5, 2018 · The XmlSecLibs library as used in the saml2 library in SimpleSAMLphp before 1.15.3 incorrectly verifies signatures on SAML assertions…30Monitor
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 |
|---|---|---|
| debian:simplesamlphp | 1.15.0-1 · Debian:12 | Package registry (OSV) |
| Packagist:simplesamlphp/simplesamlphp | 1.14.17 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · 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.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.