What is the CVSS score of CVE-2019-18849?

CVE-2019-18849 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H. EPSS exploitation probability: 1.2%.

Is there a public PoC exploit available for CVE-2019-18849?

Yes, a public proof-of-concept exploit is available for CVE-2019-18849. Prioritise patching immediately. EPSS: 1.2%.

Is there a patch available for CVE-2019-18849?

Yes, a patch is available for CVE-2019-18849. Update the affected software to the latest version immediately.

Tnef CVE-2019-18849

MEDIUM

Out-of-bounds Read (CWE-125)

2019-11-11 cve@mitre.org

Buffer Overflow Information Disclosure Tnef Fedora Ubuntu Linux Debian Linux

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Nov 11, 2019 - 04:15 nvd

MEDIUM 5.5

DescriptionNVD

In tnef before 1.4.18, an attacker may be able to write to the victim's .ssh/authorized_keys file via an e-mail message with a crafted winmail.dat application/ms-tnef attachment, because of a heap-based buffer over-read involving strdup.

AnalysisAI

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. In tnef before 1.4.18, an attacker may be able to write to the victim's .ssh/authorized_keys file via an e-mail message with a crafted winmail.dat application/ms-tnef attachment, because of a heap-based buffer over-read involving strdup. Affected products include: Tnef Project Tnef, Fedoraproject Fedora, Canonical Ubuntu Linux, Debian Debian Linux. Version information: before 1.4.18.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.