Memory corruption via mismatched GPRS payload length
Published May 27, 2025 · Updated May 29, 2025
Heap out-of-bounds write in Samsung Exynos GPRS protocol implementations allows remote attackers to corrupt memory via a crafted payload. The implementation trusts a length declared inside the payload when it differs from the payload's actual length, causing a heap write beyond the intended buffer. Network delivery requires no authentication or user interaction; Samsung has not published whether the corruption yields code execution or a service interrupt.
Summary
What happened
Heap out-of-bounds write in Samsung Exynos GPRS protocol implementations allows remote attackers to corrupt memory via a crafted payload. The implementation trusts a length declared inside the payload when it differs from the payload's actual length, causing a heap write beyond the intended buffer. Network delivery requires no authentication or user interaction; Samsung has not published whether the corruption yields code execution or a service interrupt.
The record
- CVE
- CVE-2025-22377
- Published
- May 27, 2025
- Updated
- May 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- May 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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