Security readout for executives and security teams
Plain-English summary
This issue affects SimpleSAMLphp 1.14.12 and earlier when replies are sent to non-HTTPS service providers. A network attacker positioned between systems could more easily obtain sensitive information, including protected session identifiers. The bundle does not provide a CVSS score or confirmed fixed release.
Executive priority
Prioritize review where SimpleSAMLphp supports authentication for important internal or customer-facing services. The issue is not confirmed exploited in the bundle, but HTTP-based identity flows create avoidable credential and session exposure risk.
Technical view
The CVE describes unsafe use of SimpleSAML/Utils/Crypto aesEncrypt and aesDecrypt to protect session identifiers in replies to non-HTTPS service providers. The risk is man-in-the-middle disclosure of sensitive information when HTTP service provider endpoints are permitted. No CWE, CVSS, or detailed vendor remediation text is included in the provided bundle.
Likely exposure
Exposure is likely limited to deployments of SimpleSAMLphp 1.14.12 or earlier that communicate with service providers over non-HTTPS endpoints. HTTPS-only SAML integrations appear less exposed based on the CVE description, but the bundle does not fully define all affected configurations.
Exploitation context
The source bundle does not cite public exploitation, and the CVE is not listed as KEV. Exploitation would require a man-in-the-middle position and a deployment path involving non-HTTPS service provider replies.
Researcher notes
Key unknowns are the exact fixed release, attack preconditions beyond MITM positioning, and whether local configuration can fully disable the affected path. Validate against the SimpleSAMLphp advisory before scoring or closing remediation.
Mitigation direction
- Identify all SimpleSAMLphp deployments and record their versions.
- Require HTTPS for service provider endpoints receiving replies.
- Review the SimpleSAMLphp advisory for vendor-confirmed fixed versions.
- Upgrade affected deployments according to vendor guidance.
- Retire or isolate integrations that require non-HTTPS replies.
Validation and detection
- Check whether SimpleSAMLphp version is 1.14.12 or earlier.
- Inventory configured service providers and flag any non-HTTPS reply endpoints.
- Review logs and configuration for HTTP SAML reply flows.
- Confirm vendor advisory guidance has been applied.
- Document remaining legacy HTTP dependencies and business owners.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-12870 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://simplesamlphp.org/security/201704-01CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.