LiveActive security incident?Get immediate response
CVE Record

CVE-2015-20108: xml_security.rb in the ruby-saml gem before 1.0.0 for Ruby allows XPath injection and code execution becaus...

xml_security.rb in the ruby-saml gem before 1.0.0 for Ruby allows XPath injection and code execution because prepared statements are not used.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This issue affects the ruby-saml Ruby gem before 1.0.0. A flaw in XML signature security handling could let an unauthenticated network attacker manipulate SAML processing and potentially execute code. Because SAML often protects login paths, exposure can carry business-wide identity and application risk.

Executive priority

Treat as urgent for any environment using Ruby SAML SSO. The vulnerability is critical, remotely reachable, and authentication-adjacent. First confirm whether ruby-saml before 1.0.0 exists in production, then remediate exposed identity paths before lower-risk internal services.

Technical view

xml_security.rb in ruby-saml before 1.0.0 is reported vulnerable to XPath injection and code execution because prepared statements were not used. The CVSS 3.1 score is 9.8, network exploitable, low complexity, no privileges, and no user interaction required.

Likely exposure

Most likely exposure is Ruby applications, services, or bundled products using ruby-saml versions earlier than 1.0.0 for SAML SSO. Public SSO endpoints raise urgency. The bundle does not provide a complete affected product list.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The scoring indicates remote unauthenticated exploitability, but exploit status should be treated as unconfirmed from the provided sources.

Researcher notes

The bundle identifies ruby-saml before 1.0.0, a fixing comparison to v1.0.0, and a commit reference. It does not include detailed affected downstream products, exploit telemetry, or operational indicators. Avoid assuming NetApp product impact without reading the linked advisory.

Mitigation direction

  • Inventory Ruby applications and products using the ruby-saml gem.
  • Upgrade ruby-saml to version 1.0.0 or later where applicable.
  • Check vendor advisories for bundled or appliance-managed ruby-saml usage.
  • Prioritize externally reachable SAML SSO services and administrative portals.
  • Review NetApp guidance if NetApp products are in scope.

Validation and detection

  • Check Gemfile.lock, gemspecs, SBOMs, and deployed containers for ruby-saml versions.
  • Confirm runtime services actually load the upgraded ruby-saml version.
  • Map applications exposing SAML SSO endpoints to dependency versions.
  • Review authentication logs for unusual SAML parsing or signature validation failures.
  • Track remediation evidence in vulnerability management records.
Prepared
Confidence
medium
Sources
7

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-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-20108 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
6Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2015-20108Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.