Microsoft Publisher Protection Mechanism Failure
CVE-2024-38226 is a high-severity protection mechanism failure vulnerability in Microsoft Office 2019 from Microsoft, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists version https://aka.ms/OfficeSecurityReleases as the first without the flaw, so updating Microsoft Office 2019 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on September 10, 2024, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Microsoft Office 2019 to https://aka.ms/OfficeSecurityReleases or a later version.
- Update Microsoft Office LTSC 2021 to https://aka.ms/OfficeSecurityReleases or a later version.
- Update Microsoft Publisher 2016 to 16.0.5465.1001 or a later version.
- CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Microsoft Office 2019 | 19.0.0 up to, but not including, https://aka.ms/OfficeSecurityReleases | https://aka.ms/OfficeSecurityReleases |
| Microsoft | Microsoft Office LTSC 2021 | 16.0.1 up to, but not including, https://aka.ms/OfficeSecurityReleases | https://aka.ms/OfficeSecurityReleases |
| Microsoft | Microsoft Publisher 2016 | 16.0.0 up to, but not including, 16.0.5465.1001 | 16.0.5465.1001 |
| Microsoft | Office 2019 | Not specified in the record | Not stated |
| Microsoft | Office Long Term Servicing Channel | 2021 | Not stated |
| Microsoft | Publisher | 2016 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Microsoft Publisher Security Feature Bypass Vulnerability
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Protection Mechanism Failure
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38226US Government Resource
Recent Protection Mechanism Failure vulnerabilities
- 5.4 Medium severity
- 8.6 High severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
- 6.5 Medium severity
Spotted an error? Tell us.