LiveActive security incident?Get immediate response
CVE Record

CVE-2017-2582: It was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replace...

It was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replaces special strings for obtaining attribute values with system property. This could allow an attacker to determine values of system properties at the attacked system by formatting the SAML request ID field to be the chosen system property which could be obtained in the "InResponseTo" field in the response.

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let an authenticated attacker learn Java system property values from a vulnerable Keycloak SAML response. It is an information disclosure issue, not a code-execution issue. Business urgency depends on whether exposed properties contain secrets, internal paths, service URLs, or deployment metadata.

Executive priority

Treat as a moderate confidentiality risk. Prioritize internet-facing or partner-facing SAML identity systems, especially where Java system properties may contain credentials or sensitive environment details. This should be remediated through normal security patch governance, not emergency incident response unless local evidence suggests abuse.

Technical view

Keycloak before 2.5.1 is described as replacing special strings in SAML parsing with system property values. A crafted SAML request ID can cause a selected property value to appear in the response InResponseTo field. CVSS 3.0 is 6.5 with high confidentiality impact and no integrity or availability impact.

Likely exposure

Exposure is most likely in older Keycloak deployments or Red Hat products bundling vulnerable Keycloak SAML handling. The supplied metadata is ambiguous about versions, so validate against vendor advisories and installed package versions rather than assuming only one release is affected.

Exploitation context

The source bundle shows network reachability, low privileges, no user interaction, and no KEV listing. There is no provided evidence of active exploitation. The practical risk is disclosure of system properties through SAML processing when an attacker can submit relevant SAML traffic.

Researcher notes

The core issue maps to CWE-201 information exposure. The supplied evidence supports confidentiality impact through property substitution during SAML parsing. It does not support integrity compromise, availability impact, unauthenticated exploitation, or active exploitation claims.

Mitigation direction

  • Identify Keycloak and Red Hat-bundled Keycloak deployments using SAML.
  • Check the listed Red Hat advisories for product-specific fixed packages.
  • Upgrade to vendor-designated fixed versions or supported maintained releases.
  • If patching is delayed, review vendor guidance for temporary controls.
  • Avoid storing secrets in Java system properties where possible.

Validation and detection

  • Confirm installed Keycloak versions and Red Hat package builds.
  • Verify whether SAML endpoints are enabled and externally reachable.
  • Review configuration for sensitive values exposed through system properties.
  • Check SAML logs for unusual request ID patterns, without reproducing attacks.
  • Document affected systems and remediation status by advisory.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-2582 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
19Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2017-2582Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red Hatkeycloak2.5.1Listed
Weakness

CWE details

CWE-201

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs