CVE-2025-47151
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA type confusion vulnerability exists in the lasso_node_impl_init_from_xml functionality of Entr'ouvert Lasso 2.5.1 and 2.8.2. A specially crafted SAML response can lead to an arbitrary code execution. An attacker can send a malformed SAML response to trigger this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA type confusion vulnerability exists in the lasso_node_impl_init_from_xml function of Entr'ouvert Lasso versions 2.5.1 and 2.8.2. The vulnerability is triggered during XML parsing of SAML responses, where improper type handling can be exploited to achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.5.1= 2.8.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Lasso library versionRun 'lasso-version' or 'pkg-config --modversion lasso' command, or check via Python: import lasso; print(lasso.VERSION)Affected if The installed version is exactly 2.5.1 or exactly 2.8.2
-
Verify SAML response processing is in useInspect application logs or configuration for SAML Service Provider (SP) or Identity Provider (IdP) initialization using Lasso, look for lasso_server_new or lasso_login_new callsAffected if The application processes SAML responses using Lasso library functions lasso_node_impl_init_from_xml or related XML parsing functions
-
Check if XML parsing of untrusted SAML responses occursReview application code or trace network traffic for incoming SAML Response XML that gets parsed by Lasso, particularly assertions processed via lasso_node_init_from_xmlAffected if Untrusted or externally-sourced SAML XML responses are parsed without additional validation beyond what Lasso provides
-
Identify exposed SAML endpointsReview web server configuration and application routing for endpoints that receive and process SAML responses (typically ACS URLs - Assertion Consumer Service)Affected if The application accepts and processes SAML responses at publicly accessible endpoints
You are affected if your installed Lasso version is exactly 2.5.1 or exactly 2.8.2 AND your application uses Lasso to parse incoming SAML responses from external sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Entr'ouvert Lasso to a patched version. As an interim measure, implement strict validation and sanitization of incoming SAML responses before processing.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47151 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data