Skip to content
Fencer Intel
medium 5.0

CVE-2012-6687 json

FastCGI (aka fcgi and libfcgi) 2.4.0 allows remote attackers to cause a denial of service (segmentation fault and crash) via a large number…

published 2015-02-19 11 y ago modified 2026-06-16 4 mo ago also EUVD-2012-6529

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.1%
EPSS 6.1% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

FastCGI (aka fcgi and libfcgi) 2.4.0 allows remote attackers to cause a denial of service (segmentation fault and crash) via a large number of connections.

Patch / fix

  • libfcgi Debian 14, Debian 13, Debian 12 2.4.0-8.3
  • libfcgi-perl Debian 14, Debian 13, Debian 12 0.78-2

debian advisories DEBIAN-CVE-2012-6687

  • fcgi CBL-Mariner 2.0, Azure Linux 3.0 2.4.0-7

azure linux advisories AZL-34685AZL-6418

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-6687 updated cvss 5.0

fcgi: numerous connections cause segfault DoS

  • Red Hat Ceph Storage 1.2 fcgi Red Hat Ceph Storage 1.3 fcgi
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.09% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.