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

CVE-2014-0749 has a CVSS 2.0 base score of 10.0 (Critical). CVSS vector: AV:N/AC:L/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 62.2%.

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

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

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

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

Torque Resource Manager CVE-2014-0749

CRITICAL

Buffer Overflow (CWE-119)

2014-05-16 cve@mitre.org

RCE Buffer Overflow Torque Resource Manager

10.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

10.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

May 16, 2014 - 14:55 cve.org

CRITICAL 10.0

DescriptionCVE.org

AnalysisAI

Stack-based buffer overflow in lib/Libdis/disrsi_.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 2.5.x through 2.5.13 allows remote attackers to execute arbitrary. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 62.2%.

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. Stack-based buffer overflow in lib/Libdis/disrsi_.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 2.5.x through 2.5.13 allows remote attackers to execute arbitrary code via a large count value. Affected products include: Adaptivecomputing Torque Resource Manager. Version information: through 2.5.13.

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.