External risk intelligence

Entrouvert Lasso SAML Type Confusion Allows Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-47151

Lasso is a library specifically designed to implement SAML standards for identity federation. Applications utilizing this library to process SAML responses from identity providers are inherently exposed to the public internet as part of their authentication flow, making this component a common part of public-facing identity and authentication portals.

Entrouvert Lasso

2.5.12.8.2

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the Lasso software, a component used for identity federation via SAML. This issue could allow an attacker to execute arbitrary code by sending a specially crafted response, potentially impacting systems that rely on this software for authentication. The primary concern is to confirm if our environment utilizes this specific software and is exposed to this type of threat.

  • Code execution via manipulated responses.
  • Affects identity and authentication systems.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could send a specially crafted SAML response over the network to a system using the Lasso library. This malformed response targets the `lasso_node_impl_init_from_xml` function, potentially leading to code execution.

  • Network access required.
  • Malformed SAML response triggers.
  • Arbitrary code execution risk.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute arbitrary code on a server running Entr'ouvert Lasso when processing a specially crafted SAML response. This could impact the confidentiality, integrity, and availability of the affected system.

  • System code execution.
  • Processing malformed SAML responses.
  • Complete system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

System owners and application owners are likely responsible for addressing this SAML processing vulnerability, as it impacts identity federation components. The first practical step is to identify all instances of the affected Lasso library, confirm their exposure and criticality, and then engage the accountable teams to plan remediation during a scheduled maintenance window, potentially coordinating with the vendor for updates.

  • App owners, platform teams, and security.
  • Verify Lasso instances and exposure.
  • Plan vendor coordination and patching.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Entr'ouvert Lasso?

Lasso is a software library designed to implement SAML standards, which are protocols for exchanging authentication and authorization data between parties. It is primarily used by developers to build identity federation features, enabling single sign-on capabilities where a user logs in once to access multiple web services.

What does type confusion mean in CVE-2025-47151?

This vulnerability is classified as CWE-843, which occurs when software accesses a resource using an incompatible type definition. In this specific case, the `lasso_node_impl_init_from_xml` function misinterprets data structures within a SAML response, which can cause the program to perform unintended memory operations and eventually lead to arbitrary code execution.

How is this vulnerability triggered?

An attacker triggers this bug by sending a specially crafted, malformed SAML response to a system using the affected Lasso library. It is important to note that the vulnerability is specific to the processing of these XML-based responses; simply interacting with the application or reaching its login page without sending a manipulated SAML payload does not initiate the flaw.

Why should I care about this CVE?

According to Halo Surface Signal, applications using Lasso to process SAML responses from identity providers are often located on the public internet as part of their standard authentication flow. This creates a direct path for remote attackers to interact with the vulnerable code, making it a priority for systems managing identity and authentication.

What are the first steps to address this?

Begin by auditing your infrastructure to locate any services that bundle the affected versions of the Lasso library. Once identified, evaluate their connectivity to ensure you understand which systems are reachable by external parties, then coordinate with your development or platform teams to plan for vendor-provided updates.

References