CVE-2017-2640
CVE-2017-2640 Vulnerability Analysis & Exploit Intelligence
An out-of-bounds write flaw was found in the way Pidgin before 2.12.0 processed XML content. A malicious remote server could potentially use this flaw to crash Pidgin or execute arbitrary code in the context of the pidgin process.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
6%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-787
References
5 on the record
- security.gentoo.org/glsa/201706-10
vendor-advisory, x_refsource_GENTOO
- access.redhat.com/errata/RHSA-2017:1854
vendor-advisory, x_refsource_REDHAT
- www.securityfocus.com/bid/96775
vdb-entry, x_refsource_BID
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2640
x_refsource_CONFIRM
- www.debian.org/security/2017/dsa-3806
vendor-advisory, x_refsource_DEBIAN
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.