cve.bz

CVE-2020-0813 microsoft

7.5 highEPSS 5.5%Fix available

High (7.5) in microsoft. EPSS 5.5% estimated probability of exploitation activity in the next 30 days. Fixed in Microsoft.ChakraCore 1.11.17.

An information disclosure vulnerability exists when Chakra improperly discloses the contents of its memory, which could provide an attacker with information to further compromise the user’s computer or data.To exploit the vulnerability, an attacker must know the memory address of where the object was created.The update addresses the vulnerability by changing the way certain functions handle objects in memory., aka 'Scripting Engine Information Disclosure Vulnerability'.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
5.5% (unchanged from 5.5% a week ago; 5.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 93rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-0813 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-0813?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-0813?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-0813 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vvvh-5xrm-pxffNuGetMicrosoft.ChakraCore<1.11.171.11.17

References

Check your stackJSON