What is the CVSS score of CVE-2014-2892?

CVE-2014-2892 has a CVSS 2.0 base score of 7.5 (High). CVSS vector: AV:N/AC:L/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 5.1%.

Is there a public PoC exploit available for CVE-2014-2892?

Yes, a public proof-of-concept exploit is available for CVE-2014-2892. Prioritise patching immediately. EPSS: 5.1%.

Is there a patch available for CVE-2014-2892?

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

Libmms CVE-2014-2892

HIGH

Buffer Overflow (CWE-119)

2014-04-22 cve@mitre.org

RCE Buffer Overflow Libmms

7.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/Au:N/C:P/I:P/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:N/C:P/I:P/A:P

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Apr 22, 2014 - 14:23 cve.org

HIGH 7.5

DescriptionCVE.org

Heap-based buffer overflow in the get_answer function in mmsh.c in libmms before 0.6.4 allows remote attackers to execute arbitrary code via a long line in an MMS over HTTP (MMSH) server response.

AnalysisAI

Heap-based buffer overflow in the get_answer function in mmsh.c in libmms before 0.6.4 allows remote attackers to execute arbitrary code via a long line in an MMS over HTTP (MMSH) server response. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Heap-based buffer overflow in the get_answer function in mmsh.c in libmms before 0.6.4 allows remote attackers to execute arbitrary code via a long line in an MMS over HTTP (MMSH) server response. Affected products include: Libmms Project Libmms. Version information: before 0.6.4.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.