CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.3	$0-$5k	0.00

A vulnerability classified as critical has been found in Yahoo! Messenger up to 11.5.0.228 (Messaging Software). This affects an unknown part of the component Emoticon Package Handler. The manipulation of the argument title with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Multiple stack-based buffer overflows in Yahoo! Messenger 11.5.0.228 and earlier allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via the (1) shortcut or (2) title keys in an emoticons.xml file.

The weakness was released 09/11/2015 by Julien Ahrens as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2014-7216 since 09/28/2014. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Productinfo

Type

• Messaging Software

Vendor

• Yahoo!

Name

• Messenger

Version

• 11.5.0.228

License

• free

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
unlock	unlock	unlock	unlock	unlock	unlock
unlock	unlock	unlock	unlock	unlock	unlock
unlock	unlock	unlock	unlock	unlock	unlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	unlock	unlock	unlock	unlock
Today	unlock	unlock	unlock	unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

09/28/2014 🔍
09/03/2015 +340 days 🔍
09/07/2015 +4 days 🔍
09/10/2015 +3 days 🔍
09/11/2015 +1 days 🔍
09/11/2015 +0 days 🔍
09/11/2015 +0 days 🔍
09/14/2015 +3 days 🔍
06/14/2022 +2465 days 🔍

Sourcesinfo

Vendor: yahoo.com

Advisory: 133443⛔
Researcher: Julien Ahrens
Status: Not defined

CVE: CVE-2014-7216 (🔍)
SecurityTracker: 1033544
Vulnerability Center: 52565 - Yahoo! Messenger 11.5.0.228 Remote Code Execution due to a Flaw in emoticons.xml, High
SecurityFocus: 76630 - Yahoo! Messenger CVE-2014-7216 Local Stack Buffer Overflow Vulnerability

Entryinfo

Created: 09/14/2015 10:17
Updated: 06/14/2022 20:49
Changes: 09/14/2015 10:17 (57), 12/19/2017 08:19 (8), 06/14/2022 20:49 (3)
Complete: 🔍

Discussion

Might our Artificial Intelligence support you?

Check our Alexa App!