Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 49.84% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2021
CVE-2021-26414High confidence
Windows DCOM Server Security Feature Bypass
Microsoft · Windows 10 Version 1809
4.8MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 10 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 severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Windows 10 Version 1809 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 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- SICK PSIRT: 10 affected or under-investigation product states without a fixed product state in the same current advisory
Direct vendor intelligence
1 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.
SCA-2022-0004 · CSAF 2.0 · revision 3 · finalSICK PSIRTMicrosoft vulnerability affects multiple SICK IPCs with SICK MEAC
The vendor explicitly identifies these products as affected by this CVE.
- SICK MEAC with Windows 7 (for 32-bit Systems Service Pack 1, for x64-based Systems Service Pack 1)
- SICK MEAC with Windows 8.1 (for 32-bit systems, for x64-based systems)
- SICK MEAC with Windows 10 (20H2, 21H1, 1607, 1809, 1909, 2004 for 32-bit Systems, ARM64-based Systems, x64-based Systems)
- SICK MEAC with Windows RT 8.1
- SICK MEAC with Windows Server 2008 (R2 for x64-based Systems Service Pack 1, R2 for x64-based Systems Service Pack 1,(Server Core installation), for 32-bit Systems Service Pack 2, for 32-bit Systems Service Pack 2 (Server Core installation), for x64-based Systems Service Pack 2, for x64-based Systems Service Pack 2 (Server Core installation))
- SICK MEAC with Windows Server 2012 ((GUI), (Server Core installation), R2, R2 (Server Core installation))
- SICK MEAC with Windows Server 2016 ((GUI), (Server Core installation))
- SICK MEAC with Windows Server 2019 ((GUI), (Server Core installation))
- SICK MEAC with Windows Server 20H2 (Server Core Installation)
- SICK MEAC with Windows Server 2004 (Server Core installation)
- Summary
- The CVE-2021-26414 “Windows DCOM Server Security Feature Bypass” was issued by Microsoft, that may affect the functionality of the SICK MEAC software installed on SICK IPCs. Interpretation: The vulnerability allows a remote attacker to bypass the Windows DCOM Server authentication process. Limitation: The vulnerability can only be exploited if a user operates on a CVE-2021-26414 affected Windows version and tries to access a malicious server, hosted by an attacker. The attacker would have to host a specially crafted server share or website. It is not possible for an attacker to force the user to visit this specially crafted server share or website. Only by convincing them, typically by way of an enticement in an email or chat message, an exploitation is possible.
- Remediation
- Microsoft is addressing this vulnerability in a phased rollout of Windows security updates. Under the current schedule, the hardening changes can be disabled until March 14, 2023: - June 8, 2021: Hardening changes **disabled by default** but with the ability to enable them using a registry key. - June 14, 2022: Hardening changes **enabled by default** but with the ability to disable them using a registry key. - March 14, 2023: Hardening changes **enabled** by default **with no ability to disable them**. By this point, you must resolve any compatibility issues with the hardening changes and applications in your environment. Prior to the March 2023 release, the hardening change will be disabled if the registry key HKEY_LOCAL_MACHINE \\ SOFTWARE \\ Microsoft \\ Ole \\ AppCompat \\ RequireIntegrityActivationAuthenticationLevel is undefined or 0, and enabled, if set to 1. A reboot is required after making any changes to the registry key. **Recommended measures:** Given the moderate risk (a user having to deliberately access a malicious server), SICK recommends deactivating the hardening by using the above registry key, until it has been confirmed that the hardening does not adversely affect the MEAC functionality. SICK will then inform customers in an updated version of this security advisory. In a subset of Windows versions with release dates newer than between August 2021 and October 2021, depending on the Windows version, customers can identify vulnerable installations by checking the Windows event log for messages.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 10 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
Windows DCOM Server Security Feature Bypass
What
Windows DCOM Server Security Feature Bypass
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Windows DCOM Server Security Feature Bypass
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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
- a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration. - CWE not yet assigned
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
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
- Affected
- SICK MEAC with Windows 7 (for 32-bit Systems Service Pack 1, for x64-based Systems Service Pack 1)
- SICK MEAC with Windows 8.1 (for 32-bit systems, for x64-based systems)
- SICK MEAC with Windows 10 (20H2, 21H1, 1607, 1809, 1909, 2004 for 32-bit Systems, ARM64-based Systems, x64-based Systems)
- SICK MEAC with Windows RT 8.1
- SICK MEAC with Windows Server 2008 (R2 for x64-based Systems Service Pack 1, R2 for x64-based Systems Service Pack 1,(Server Core installation), for 32-bit Systems Service Pack 2, for 32-bit Systems Service Pack 2 (Server Core installation), for x64-based Systems Service Pack 2, for x64-based Systems Service Pack 2 (Server Core installation))
- SICK MEAC with Windows Server 2012 ((GUI), (Server Core installation), R2, R2 (Server Core installation))
- SICK MEAC with Windows Server 2016 ((GUI), (Server Core installation))
- SICK MEAC with Windows Server 2019 ((GUI), (Server Core installation))
- SICK MEAC with Windows Server 20H2 (Server Core Installation)
- SICK MEAC with Windows Server 2004 (Server Core installation)
- 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Jun 2021 · Last source change 3 Aug 2024, 20:26 UTC · CWE not yet assigned
CVE recordCVE.org · 5.1
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-2021-13220
Product sourceVendor CSAF · SICK PSIRT
Remediation sourceVendor CSAF · SICK PSIRT
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: added remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf; removed remediation: msrc.microsoft.com/CVE-2021-26414.SICK PSIRT ↗
- Before
- remediation: msrc.microsoft.com/CVE-2021-26414
- After
- remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf
CVE published
Fixed release or patch reference recorded
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.