Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 1.23% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-36793High confidence
Visual Studio Remote Code Execution Vulnerability
Microsoft · Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
Official source articles: Siemens SSA-341067 ↗ · Siemens SSA-556635 ↗. Check the applicable product and release in the original source.
7.8HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| NuGetMicrosoft.NETCore.App.Runtime.win-arm64 | ECOSYSTEM: introduced 7.0.0; fixed 7.0.11 | 7.0.11 | OSV record ↗aggregator derived · 3 Dec 2024 |
| NuGetMicrosoft.NETCore.App.Runtime.win-arm64 | ECOSYSTEM: introduced 6.0.0; fixed 6.0.22 | 6.0.22 | OSV record ↗aggregator derived · 3 Dec 2024 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x64 | ECOSYSTEM: introduced 7.0.0; fixed 7.0.11 | 7.0.11 | OSV record ↗aggregator derived · 3 Dec 2024 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x64 | ECOSYSTEM: introduced 6.0.0; fixed 6.0.22 | 6.0.22 | OSV record ↗aggregator derived · 3 Dec 2024 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x86 | ECOSYSTEM: introduced 7.0.0; fixed 7.0.11 | 7.0.11 | OSV record ↗aggregator derived · 3 Dec 2024 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x86 | ECOSYSTEM: introduced 6.0.0; fixed 6.0.22 | 6.0.22 | OSV record ↗aggregator derived · 3 Dec 2024 |
Direct vendor intelligence
2 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
SSA-341067 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-341067: Multiple vulnerabilities in third-party components in ST7 ScadaConnect before V1.1
The vendor explicitly identifies these products as affected by this CVE.
- ST7 ScadaConnect (6NH7997-5DA10-0AA0)
- Summary
- Visual Studio Remote Code Execution Vulnerability
- Remediation
- Update to V1.1 or later version
SSA-556635 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-556635: Multiple Vulnerabilities in Telecontrol Server Basic before V3.1.2.0
The vendor explicitly identifies these products as affected by this CVE.
- TeleControl Server Basic V3
- Summary
- Visual Studio Remote Code Execution Vulnerability
- Remediation
- Update to V3.1.2 or later version
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Visual Studio Remote Code Execution Vulnerability
What
Visual Studio Remote Code Execution Vulnerability
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
What
Visual Studio Remote Code Execution Vulnerability
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Heap-based Buffer Overflow → execute code or commands in the affected security context
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-122 ↗
CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 12 Sept 2023 · Last source change 30 Oct 2025, 18:18 UTC · CWE-122 · Heap-based Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-2498
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceOther authority
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Siemens ProductCERT ↗
- Before
- 15.9.0 < 15.9.57; 17.2.0 < 17.2.21; 16.11.0 < 16.11.30; 17.4.0 < 17.4.13; 7.0.0 < 7.0.13; 6.0.0 < 6.0.24; 7.2.0 < 7.2.12; 17.6.0 < 17.6.9 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- 15.9.0 < 15.9.57; 17.2.0 < 17.2.21; 16.11.0 < 16.11.30; 17.4.0 < 17.4.13; 7.0.0 < 7.0.13; 6.0.0 < 6.0.24; 7.2.0 < 7.2.12; 17.6.0 < 17.6.9 · Fixed: Update to V3.1.2 or later version
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.