What is the CVSS score of CVE-2016-1901?

CVE-2016-1901 has a CVSS 3.0 base score of 9.8 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 4.4%.

Is there a public PoC exploit available for CVE-2016-1901?

Yes, a public proof-of-concept exploit is available for CVE-2016-1901. Prioritise patching immediately. EPSS: 4.4%.

Is there a patch available for CVE-2016-1901?

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

Fedora CVE-2016-1901

CRITICAL

Buffer Overflow (CWE-119)

2016-01-20 cve@mitre.org

Buffer Overflow Fedora Cgit

9.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jan 20, 2016 - 16:59 cve.org

CRITICAL 9.8

DescriptionCVE.org

AnalysisAI

Integer overflow in the authenticate_post function in CGit before 0.12 allows remote attackers to have unspecified impact via a large value in the Content-Length HTTP header, which triggers a buffer. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, 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. Integer overflow in the authenticate_post function in CGit before 0.12 allows remote attackers to have unspecified impact via a large value in the Content-Length HTTP header, which triggers a buffer overflow. Affected products include: Fedoraproject Fedora, Cgit Project Cgit. Version information: before 0.12.

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.