What is the CVSS score of CVE-2013-4365?

CVE-2013-4365 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: 6.7%.

Is there a patch available for CVE-2013-4365?

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

Mod Fcgid CVE-2013-4365

HIGH

Out-of-bounds Write (CWE-787)

2013-10-17 secalert@redhat.com

Buffer Overflow Apache Memory Corruption Mod Fcgid Debian Linux Cloud Opensuse Linux Enterprise Software Development Kit

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

Oct 17, 2013 - 23:55 cve.org

HIGH 7.5

DescriptionCVE.org

AnalysisAI

Heap-based buffer overflow in the fcgid_header_bucket_read function in fcgid_bucket.c in the mod_fcgid module before 2.3.9 for the Apache HTTP Server allows remote attackers to have an unspecified. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, low attack complexity. This Out-of-bounds Write vulnerability could allow attackers to write data beyond allocated buffer boundaries leading to code execution or crashes.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Write (CWE-787), which allows attackers to write data beyond allocated buffer boundaries leading to code execution or crashes. Heap-based buffer overflow in the fcgid_header_bucket_read function in fcgid_bucket.c in the mod_fcgid module before 2.3.9 for the Apache HTTP Server allows remote attackers to have an unspecified impact via unknown vectors. Affected products include: Apache Mod Fcgid, Debian Debian Linux, Suse Cloud, Opensuse, Suse Linux Enterprise Software Development Kit. Version information: before 2.3.9.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).