CVE-2019-0900
Last modified
CVE-2019-0900 is a vulnerability of currently unknown severity. A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka 'Jet Database Engine Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0889, CVE-2019-0890, CVE-2019-0891, CVE-2019-0893, CVE-2019-0894, CVE-2019-0895, CVE-2019-0896, CVE-2019-0897, CVE-2019-0898, CVE-2019-0899, CVE-2019-0901, CVE-2019-0902.. EPSS estimates a 13.71% chance of exploitation in the next 30 days.
Description
A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka 'Jet Database Engine Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0889, CVE-2019-0890, CVE-2019-0891, CVE-2019-0893, CVE-2019-0894, CVE-2019-0895, CVE-2019-0896, CVE-2019-0897, CVE-2019-0898, CVE-2019-0899, CVE-2019-0901, CVE-2019-0902.
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Microsoft | Windows 10 | All versions | — |
| Microsoft | Windows 10 | 1607 | — |
| Microsoft | Windows 10 | 1703 | — |
| Microsoft | Windows 10 | 1709 | — |
| Microsoft | Windows 10 | 1803 | — |
| Microsoft | Windows 10 | 1809 | — |
| Microsoft | Windows 10 | 1903 | — |
| Microsoft | Windows 7 | All versions | Sp1 |
| Microsoft | Windows 8.1 | All versions | — |
| Microsoft | Windows Rt 8.1 | All versions | — |
| Microsoft | Windows Server 2008 | All versions | Sp2 |
| Microsoft | Windows Server 2008 | r2 | Sp1 |
| Microsoft | Windows Server 2012 | All versions | — |
| Microsoft | Windows Server 2012 | r2 | — |
| Microsoft | Windows Server 2016 | All versions | — |
| Microsoft | Windows Server 2016 | 1803 | — |
| Microsoft | Windows Server 2016 | 1903 | — |
| Microsoft | Windows Server 2019 | All versions | — |
References
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0900Patch, Vendor Advisory
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0900Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-0900?
How severe is CVE-2019-0900?
How do I fix CVE-2019-0900?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-0894A remote code execution vulnerability exists when the Window…
- CVE-2019-0895A remote code execution vulnerability exists when the Window…
- CVE-2019-0896A remote code execution vulnerability exists when the Window…
- CVE-2019-0897A remote code execution vulnerability exists when the Window…
- CVE-2019-0898A remote code execution vulnerability exists when the Window…
- CVE-2019-0899A remote code execution vulnerability exists when the Window…
- CVE-2019-0901A remote code execution vulnerability exists when the Window…
- CVE-2019-0902A remote code execution vulnerability exists when the Window…
- CVE-2019-0903A remote code execution vulnerability exists in the way that…8.8
- CVE-2019-0904A remote code execution vulnerability exists when the Window…7.8
- CVE-2019-0905A remote code execution vulnerability exists when the Window…7.8
- CVE-2019-0906A remote code execution vulnerability exists when the Window…7.8
Are you affected by CVE-2019-0900?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
