CVE Alert: CVE-2025-46705 – Entr’ouvert – Lasso

CVE-2025-46705

HIGHNo exploitation known

A denial of service vulnerability exists in the g_assert_not_reached functionality of Entr'ouvert Lasso 2.5.1 and 2.8.2. A specially crafted SAML assertion response can lead to a denial of service. An attacker can send a malformed SAML response to trigger this vulnerability.

CVSS v3.1 (7.5)
AV NETWORK · AC LOW · PR NONE · UI NONE · S UNCHANGED
Vendor
Entr’ouvert
Product
Lasso
Versions
2.5.1 | 2.8.2
CWE
CWE-617, CWE-617: Reachable Assertion
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2025-11-05T14:56:55.535Z
Updated
2025-11-05T22:36:34.501Z

AI Summary Analysis

Risk verdict

High risk of remote denial of service via unauthenticated, network-based SAML response handling; exploitation status appears not active at present, but impact is high.

Why this matters

A crafted SAML response can crash the service, disrupting authentication flows and potentially taking downstream applications offline. Organisations relying on SAML-based SSO may suffer outages during peak login windows, eroding continuity and customer trust.

Most likely attack path

Remote attacker sends malformed SAML assertions to the service’s network-facing endpoint; no privileges or user interaction required, and no credential use. The vulnerability’s reach is scope-unchanged, so a DoS condition could rapidly exhaust resources and cause service unavailability without touching other components.

Who is most exposed

deployments that expose SAML endpoints to the internet or to partner networks are most at risk, especially where Lasso acts as IdP/SP in customer-facing or high-availability environments.

Detection ideas

  • Spike in failures or crashes triggered by SAML endpoint processing.
  • Logs showing g_assert_not_reached or assertion-failure events.
  • Elevated CPU/memory usage on the identity service following SAML traffic bursts.
  • Anomalous traffic patterns to SAML endpoints (unusual payloads, malformed responses).
  • Increased authentication errors during incidents.

Mitigation and prioritisation

  • Apply vendor patch or upgrade to a fixed release as soon as available; verify compatibility in staging first.
  • Implement input validation and strict SAML response handling; enable rate-limiting and WAF rules for the SAML endpoint.
  • Monitor and alert on SAML processing crashes; establish a hotfix window if DoS signals appear.
  • Review change-management plans for identity services; prepare rollback and testing scripts.
  • If KEV or EPSS data later indicate exploitation risk, treat as priority 1.

Support Our Work

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

AI APIs OSINT driven New features