CVE-2023-35641
Microsoft Windows Server 2008 r2
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-35641 is a high-severity Incorrect Calculation (CWE-682) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-35641 is a remote code execution vulnerability in the Internet Connection Sharing (ICS) component of Windows. It carries a CVSS 3.1 base score of 8.8 and is associated with CWE-682. The flaw permits an attacker to execute arbitrary code on an affected system when ICS is enabled.
An attacker with adjacent-network access and no privileges or user interaction can exploit the issue to obtain full control over confidentiality, integrity, and availability on the target. The attack vector is limited to the local network segment rather than the broader internet.
Microsoft’s Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-35641 supplies official mitigation guidance and patch information for the vulnerability.
The associated EPSS score remains flat at 0.0522 with no material increase observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-39641
Vulnerability Data
Internet Connection Sharing (ICS) Remote Code Execution Vulnerability
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle mandates verification steps that catch incorrect calculations before they reach production.
A.8.26 requires that security requirements (including resilience against attacks such as buffer overflows or SQL injection) be identified during development or acquisition; it does not itself enforce correct calculations or stop an arithmetic error from being introduced or exploited.
A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, and design reviews) but does not itself remove or rewrite an incorrect calculation already present in first-party code; that is a code defect class reached only by testing or remediation controls per the locus rule.
Secure coding standards directly prohibit unsafe arithmetic and require defensive checks against incorrect results.
Security testing in development and acceptance can detect calculation flaws before deployment.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-682, a pillar-level weakness, and none of its children carries one either.