CVE-2013-2877
What it is
parser.c in libxml2 before 2.9.0, as used in Google Chrome before 28.0.1500.71 and other products, allows remote attackers to cause a denial of service (out-of-bounds read) via a document that ends abruptly, related to the lack of certain checks for the XML_PARSER_EOF state.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 5.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 5.0% in the next 30 days (EPSS).
- Severity: 5.0 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 5.0% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- Google Chrome ≤ 28.0.1500.70
- Google Chrome 28.0.1500.0
- Google Chrome 28.0.1500.2
- Google Chrome 28.0.1500.3
- Google Chrome 28.0.1500.4
- Google Chrome 28.0.1500.5
- Google Chrome 28.0.1500.6
- Google Chrome 28.0.1500.8
Attack profile CVSS 2.0 · 5.0
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2013-2877.md and follow it. Check whether this project is affected by CVE-2013-2877. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- ftp://xmlsoft.org/libxml2/libxml2-2.9.0.tar.gz
- http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=e5d7f7e5dc21d3ae7be3cbb949ac4d8701e06de1
- http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00002.html
- http://lists.opensuse.org/opensuse-updates/2013-07/msg00063.html
- http://lists.opensuse.org/opensuse-updates/2013-07/msg00077.html
- http://seclists.org/fulldisclosure/2014/Dec/23
- http://secunia.com/advisories/54172
- http://secunia.com/advisories/55568
- http://www.debian.org/security/2013/dsa-2724
- http://www.debian.org/security/2013/dsa-2779
- http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- http://www.securityfocus.com/archive/1/534161/100/0/threaded
- http://www.securityfocus.com/bid/61050
- http://www.ubuntu.com/usn/USN-1904-1
- http://www.ubuntu.com/usn/USN-1904-2
- http://www.vmware.com/security/advisories/VMSA-2014-0012.html
- https://code.google.com/p/chromium/issues/detail?id=229019
- ftp://xmlsoft.org/libxml2/libxml2-2.9.0.tar.gz
- http://git.chromium.org/gitweb/?p=chromium/chromium.git%3Ba=commit%3Bh=e5d7f7e5dc21d3ae7be3cbb949ac4d8701e06de1
- http://googlechromereleases.blogspot.com/2013/07/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00002.html
- http://lists.opensuse.org/opensuse-updates/2013-07/msg00063.html
- http://lists.opensuse.org/opensuse-updates/2013-07/msg00077.html
- http://seclists.org/fulldisclosure/2014/Dec/23