Pidgin Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

2.5.027
2.5.227
2.5.126
2.10.721
2.020

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix94
Temporary Fix0
Workaround0
Unavailable0
Not Defined10

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept13
Unproven13
Not Defined78

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local15
Adjacent0
Network89

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High0
Low25
None79

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required0
None104

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤45
≤513
≤636
≤714
≤821
≤91
≤1014

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤30
≤46
≤525
≤626
≤721
≤811
≤95
≤1010

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤30
≤412
≤56
≤639
≤79
≤823
≤91
≤1014

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤44
≤50
≤615
≤70
≤80
≤913
≤103

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k33
<2k17
<5k53
<10k0
<25k0
<50k1
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k104
<2k0
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (70): 0.1, 0.1.2, 0.2, 0.2.1, 2, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.2, 2.2.1, 2.2.2, 2.3, 2.3.1, 2.4, 2.4.1, 2.4.2, 2.4.3, 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 2.5.6, 2.5.7, 2.5.8, 2.5.9, 2.6, 2.6.1, 2.6.2, 2.6.4, 2.6.5, 2.6.6, 2.7, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9, 2.8, 2.9, 2.10, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.10.6, 2.10.7, 2.10.8, 2.10.9, 2.11, 2.14, 2.14.1, 2.14.2, 2.14.3, 2.14.4, 2.14.5, 2.14.6, 2.14.7, 2.14.8, 3.2, 4, 4.0.1

Software Type: Messaging Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
06/03/20225.65.4Pidgin DNS Response certificate validation$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-26491
11/20/20194.44.0Pidgin dbus cleartext transmission$0-$5k$0-$5kProof-of-ConceptNot Defined0.04CVE-2012-1257
03/29/20177.26.9Pidgin MXIT inadequate encryption$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2016-2379
03/15/20179.89.0Pidgin out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2017-2640
01/06/20175.14.9Pidgin MXIT Protocol path traversal$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2016-4323
01/06/20175.25.0Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2016-2380
01/06/20177.77.3Pidgin MXIT Protocol memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2016-2378
01/06/20177.77.3Pidgin MXIT Protocol memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2016-2377
01/06/20177.77.3Pidgin MXIT Protocol memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2016-2376
01/06/20176.36.1Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2016-2375
01/06/20177.77.3Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.01CVE-2016-2374
01/06/20175.65.4Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2016-2373
01/06/20176.66.4Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2016-2372
01/06/20177.77.3Pidgin MXIT Protocol out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2016-2371
01/06/20175.65.4Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2016-2370
01/06/20175.65.4Pidgin MXIT Protocol null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.01CVE-2016-2369
01/06/20177.77.3Pidgin MXIT Protocol memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2016-2368
01/06/20176.66.4Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2016-2367
01/06/20175.65.4Pidgin MXIT Protocol out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2016-2366
01/06/20175.65.4Pidgin MXIT Protocol null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2016-2365
06/21/20163.33.2Pidgin MXIT Suggested Contacts Memory information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix1.11CVE-2016-2375
06/21/20166.76.6Pidgin MXIT MultiMX Message memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix1.26CVE-2016-2374
06/21/20164.64.5Pidgin MXIT Contact Mood denial of service$0-$5k$0-$5kNot DefinedOfficial Fix1.26CVE-2016-2373
06/21/20164.64.5Pidgin MXIT File Transfer Memory information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix1.26CVE-2016-2372
06/21/20166.76.6Pidgin MXIT Extended Profiles memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.89CVE-2016-2371

79 more entries are not shown

Interested in the pricing of exploits?

See the underground prices here!