CVE-2023-28299 | Visual Studio Spoofing Vulnerability

Visual Studio Spoofing Vulnerability

Published: 2023-04-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-28299 is rated Low Risk (36.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.54%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-28299

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.19% 0.54% +0.35%
2 2026-06-14 0.11% 0.19% +0.08%
3 2025-11-21 — 0.11% —

Full EPSS history (15 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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: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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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: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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2023-28299

Affected software / configurations for CVE-2023-28299

Vendor Product Version Raw CPE
microsoft visual_studio_2017 >= 15.0, < 15.9.54 cpe:2.3:a:microsoft:visual_studio_2017:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.0, < 16.11.26 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.0, < 17.0.21 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.2.0, < 17.2.15 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:-:*:*
microsoft visual_studio_2022 >= 17.4.0, < 17.4.7 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:-:*:*
microsoft visual_studio_2022 >= 17.5.0, < 17.5.4 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:-:*:*

References for CVE-2023-28299

cvelogic Threat Intelligence