Code execution via JT buffer overrun
Published Jan 13, 2022 · Updated Aug 4, 2024
Out-of-bounds write in Bentley View 10.15.0.75 allows remote attackers to execute code after a user opens a crafted JT file. The JT parser writes crafted file data past the end of an allocated buffer, corrupting adjacent process memory. Execution requires user interaction and runs with the privileges of the Bentley View process, exposing data and system actions available to that user.
Summary
What happened
Out-of-bounds write in Bentley View 10.15.0.75 allows remote attackers to execute code after a user opens a crafted JT file. The JT parser writes crafted file data past the end of an allocated buffer, corrupting adjacent process memory. Execution requires user interaction and runs with the privileges of the Bentley View process, exposing data and system actions available to that user.
The record
- CVE
- CVE-2021-34921
- Published
- Jan 13, 2022
- Updated
- Aug 4, 2024
- Vendor
- Bentley Systems
- Product
- Bentley View
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.15.0.75
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.
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