Graphviz: Out-of-bounds Read
CVE-2023-46045 is a high-severity out-of-bounds read vulnerability in Graphviz, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.0 as the first without the flaw, so updating Graphviz to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.81% chance of exploitation within 30 days, higher than 58% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Graphviz to 10.0.0 or a later version.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
Graphviz 2.36.0 through 9.x before 10.0.1 has an out-of-bounds read via a crafted config6a file. NOTE: exploitability may be uncommon because this file is typically owned by root.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- seclists.org/fulldisclosure/2024/Jan/73Mailing List, Third Party Advisory
Technical write-ups (may include proof of concept)
- gitlab.com/graphviz/graphviz/-/issues/2441Exploit, Issue Tracking
Other references
- seclists.org/fulldisclosure/2024/Feb/24
- seclists.org/fulldisclosure/2024/Feb/24
- openwall.com/lists/oss-security/2024/02/01/2Mailing List
- packetstormsecurity.com/files/176816/graphviz-2.43.0-Buffer-Overflow-Code-Execution.html
- seclists.org/fulldisclosure/2024/Jan/62
- seclists.org/fulldisclosure/2024/Jan/73
Recent Out-of-bounds Read vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 9.6 Critical severity
- 9.6 Critical severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.