CVE-2023-0687 — A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This...
A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This vulnerability affects the function __monstartup of the file gmon.c of the component Call Graph Monitor. The manipulation leads to buffer overflow. It is recommended to apply a patch to fix this issue. VDB-220246 is the identifier assigned to this vulnerability. NOTE: The real existence of this vulnerability is still doubted at the moment. The inputs that induce this vulnerability are basically addresses of the running application that is built with gmon enabled. It's basically trusted input or input that needs an actual security flaw to be compromised or controlled.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1.1% (30-day exploitation probability)+10
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — patchwork.sourceware.org (NIST National Vulnerability Database)
- Documented patch — sourceware.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Gnu C Library, Gnu Glibc).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.6 | CVSS 3.1 | Medium | 1.2 | 3.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 4.6 | CVSS 3.1 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 4.6 | CVSS 3.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 4.0 | CVSS 2.0 | Medium | 2.5 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · gnu/c library
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · gnu/glibc
- CVSS changed · 9.8
- Source status changed · → Modified
- Record created in this database
- 2023
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
9 on the record
- sourceware.org/bugzilla/show_bug.cgi
- patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/
- nvd.nist.gov/vuln/detail/CVE-2023-0687
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- vuldb.com/
- patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo@yuriev.ru
- github.com/advisories/GHSA-5r4p-4pqv-gqhw
- patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru
- vuldb.com/
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-6238 Buffer overread in ns_printrrf with corrupted RDATA field Apr 28, 2026
- High CVE-2026-5435 Potential buffer overflow in ns_sprintrrf TSIG handling path Apr 28, 2026
- High CVE-2026-5928 Potential buffer under-read in ungetwc Apr 20, 2026
- Critical CVE-2026-5450 scanf %mc off-by-one heap buffer overflow Apr 20, 2026
- High CVE-2026-4046 iconv crash due to assertion failure with untrusted input Mar 30, 2026
- Medium CVE-2026-4438 gethostbyaddr and gethostbyaddr_r return invalid DNS hostnames Mar 20, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-0687 is "A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This...", rated Critical. It affects C Library (Gnu); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 1.09% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.