GNU Emacs up to 25.2 Email enriched.el XML Element command injection

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.4$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in GNU Emacs up to 25.2. The affected element is an unknown function of the file lisp/textmodes/enriched.el of the component Email Handler. This manipulation as part of XML Element causes command injection. This vulnerability is tracked as CVE-2017-14482. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in GNU Emacs up to 25.2 (Word Processing Software) and classified as critical. Affected by this vulnerability is some unknown functionality of the file lisp/textmodes/enriched.el of the component Email Handler. The manipulation as part of a XML Element leads to a command injection vulnerability. The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

GNU Emacs before 25.3 allows remote attackers to execute arbitrary code via email with crafted "Content-Type: text/enriched" data containing an x-display XML element that specifies execution of shell commands, related to an unsafe text/enriched extension in lisp/textmodes/enriched.el, and unsafe Gnus support for enriched and richtext inline MIME objects in lisp/gnus/mm-view.el. In particular, an Emacs user can be instantly compromised by reading a crafted email message (or Usenet news article).

The bug was discovered 09/04/2017. The weakness was disclosed 09/14/2017 (oss-sec). The advisory is shared at openwall.com. This vulnerability is known as CVE-2017-14482 since 09/14/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 10 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 103362 (CentOS 7 : emacs (CESA-2017:2771)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 351110 (Amazon Linux Security Advisory for emacs: ALAS-2017-912).

Upgrading to version 25.3 eliminates this vulnerability. A possible mitigation has been published 6 days after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (103362). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.4

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Command injection
CWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 103362
Nessus Name: CentOS 7 : emacs (CESA-2017:2771)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 53377
OpenVAS Name: Debian Security Advisory DSA 3975-1 (emacs25 - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Emacs 25.3
Patch: git.savannah.gnu.org

Timelineinfo

09/04/2017 🔍
09/14/2017 +10 days 🔍
09/14/2017 +0 days 🔍
09/14/2017 +0 days 🔍
09/15/2017 +1 days 🔍
09/20/2017 +5 days 🔍
09/21/2017 +1 days 🔍
12/29/2022 +1925 days 🔍

Sourcesinfo

Vendor: gnu.org

Advisory: RHSA-2017:2771
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-14482 (🔍)
GCVE (CVE): GCVE-0-2017-14482
GCVE (VulDB): GCVE-100-106717

OVAL: 🔍

Entryinfo

Created: 09/15/2017 09:14
Updated: 12/29/2022 09:18
Changes: 09/15/2017 09:14 (77), 11/16/2019 20:20 (3), 12/29/2022 09:18 (5)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!