Authentication bypass via arbitrary SAML signing keys
Published Jul 15, 2019 · Updated Aug 4, 2024
Authentication bypass in Microsoft WCF and WIF allows remote attackers to forge SAML tokens with arbitrary symmetric signing keys. The token-validation path accepts a SAML signature made with an attacker-selected symmetric key instead of requiring a trusted configured key. A reachable application must use an affected WCF or WIF SAML implementation; successful exploitation lets forged identity assertions pass authentication and authorize protected actions.
Summary
What happened
Authentication bypass in Microsoft WCF and WIF allows remote attackers to forge SAML tokens with arbitrary symmetric signing keys. The token-validation path accepts a SAML signature made with an attacker-selected symmetric key instead of requiring a trusted configured key. A reachable application must use an affected WCF or WIF SAML implementation; successful exploitation lets forged identity assertions pass authentication and authorize protected actions.
The record
- CVE
- CVE-2019-1006
- Published
- Jul 15, 2019
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows Server, version 1903 (Server Core installation)
- Classifications
- CWE-295, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2019CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo