Memory exhaustion via unreleased Base64 buffer
Published Nov 5, 2025 · Updated Nov 5, 2025
Memory leak in Lasso 2.5.1 allows remote attackers to exhaust memory by sending a malformed SAML response to its message parser. lasso_node_init_from_message_with_format allocates a Base64-decoding buffer with g_malloc and leaves it unreleased on successful decoding paths. Repeated unauthenticated network requests can deplete the hosting process's memory and interrupt the SAML-dependent service, without reported data disclosure or modification.
Summary
What happened
Memory leak in Lasso 2.5.1 allows remote attackers to exhaust memory by sending a malformed SAML response to its message parser. lasso_node_init_from_message_with_format allocates a Base64-decoding buffer with g_malloc and leaves it unreleased on successful decoding paths. Repeated unauthenticated network requests can deplete the hosting process's memory and interrupt the SAML-dependent service, without reported data disclosure or modification.
The record
- CVE
- CVE-2025-46784
- Published
- Nov 5, 2025
- Updated
- Nov 5, 2025
- Vendor
- Entr'ouvert
- Product
- Lasso
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo