Code execution via wrapped bn_grow allocation size
Published Sep 1, 2023 · Updated Oct 1, 2024
Integer overflow in RELIC before commit 34580d840469361ba9b5f001361cad659687b9ab allows remote attackers to execute arbitrary code through bn_grow. The function calculates a realloc size using an integer-limited digit count, so a large growth request wraps to a small allocation that later operations treat as larger. Exploitation requires a consuming application to let untrusted input drive an affected big-number operation; subsequent heap corruption can crash the process or execute code.
Summary
What happened
Integer overflow in RELIC before commit 34580d840469361ba9b5f001361cad659687b9ab allows remote attackers to execute arbitrary code through bn_grow. The function calculates a realloc size using an integer-limited digit count, so a large growth request wraps to a small allocation that later operations treat as larger. Exploitation requires a consuming application to let untrusted input drive an affected big-number operation; subsequent heap corruption can crash the process or execute code.
The record
- CVE
- CVE-2023-36326
- Published
- Sep 1, 2023
- Updated
- Oct 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2023CVE publishedPublication date reported by the CVE source.
- Oct 1, 2024Record 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