CVE-2023-0687

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.

Published: 2023-02-06 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-0687 is rated Moderate Risk (40.9/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.10%). EPSS rose +1.04% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-0687

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 1.10% +1.04%
2 2025-11-21 0.53% 0.06% -0.47%
3 2025-11-18 — 0.53% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-0687

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.6 3.1 MEDIUM
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.2 3.4 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
4.0 2.0 MEDIUM
AV:A/AC:H/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 2.5 6.4 [email protected]

Weakness enumeration for CVE-2023-0687

OS Trackers for CVE-2023-0687

vendor priority summary link
redhat — — https://access.redhat.com/security/cve/CVE-2023-0687
suse low CVE-2023-0687 severity low: SUSE including 540 source package names (0.23.0.3.2.423:glibc-2.31-150300.46.1, 0.23.1-12.3:binutils-2.41-150100.7.46.1, …), 2614 product×package rows across 443 product lines (Container bci/bci-base-fips, Container bci/bci-busybox, … (443 product lines)): Fixed 2291, Known Not Affected 181, Known Affected 142. https://www.suse.com/security/cve/CVE-2023-0687/
ubuntu low CVE-2023-0687 low priority: Ubuntu including 2 source packages (eglibc, glibc), 15 status rows across 8 suites (bionic, focal, jammy, kinetic, lunar, trusty, upstream, xenial): not-affected 9, DNE 5, ignored 1. https://ubuntu.com/security/CVE-2023-0687

Affected software / configurations for CVE-2023-0687

Vendor Product Version Raw CPE
gnu glibc < 2.38 cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*

References for CVE-2023-0687

URL Tags
https://patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/ Patch
https://sourceware.org/bugzilla/show_bug.cgi?id=29444 Issue Tracking Patch Third Party Advisory
https://vuldb.com/?ctiid.220246 Permissions Required Third Party Advisory
https://vuldb.com/?id.220246 Permissions Required Third Party Advisory
cvelogic Threat Intelligence