Security readout for executives and security teams
Plain-English summary
Bentley View 10.16.0.80 can leak sensitive information when a user opens a malicious JT file or visits a malicious page. The issue may also support code execution when combined with other vulnerabilities, so affected workstations handling CAD/model files deserve prompt attention.
Executive priority
Treat this as a high-priority workstation risk for teams using Bentley View with external design files. It is not evidenced as actively exploited, but the confidentiality impact and possible code-execution chaining justify timely remediation planning.
Technical view
CVE-2021-46570 is a CWE-457 uninitialized memory issue in Bentley View JT file parsing. It requires user interaction and is scored CVSS 7.8 high. The supplied description says attackers can use it with other vulnerabilities to execute code in the current process.
Likely exposure
Exposure is likely limited to endpoints running Bentley View 10.16.0.80, especially users who receive or inspect JT files from customers, suppliers, or external sources.
Exploitation context
The supplied sources do not show active exploitation, and KEV status is false. Exploitation requires persuading a user to open a malicious file or page, making phishing and file-sharing workflows the main concern.
Researcher notes
Key evidence is narrow: affected product and version, JT parser memory initialization flaw, ZDI-CAN-15364/ZDI-22-157 lineage, and user-interaction requirement. The supplied bundle does not name a specific fixed version or standalone mitigation.
Mitigation direction
- Check Bentley advisory BE-2021-0005 for vendor updates or workarounds.
- Remove or replace Bentley View 10.16.0.80 where it is not required.
- Avoid opening unsolicited JT files or related links on affected systems.
- Apply least privilege for users who handle untrusted design files.
- Use mail and web controls to reduce delivery of suspicious JT content.
Validation and detection
- Inventory endpoints for Bentley View 10.16.0.80.
- Confirm whether affected users handle JT files from external parties.
- Review Bentley guidance before marking systems remediated.
- Check security telemetry for suspicious JT attachments or links.
- Document compensating controls where immediate remediation is unavailable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-457: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-46570 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.8HighVector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.bentley.com/en/common-vulnerability-exposure/BE-2021-0005CVE reference · x_refsource_MISC
- https://www.zerodayinitiative.com/advisories/ZDI-22-157/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Uninitialized Variable
Use of Uninitialized Variable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.