Skip to content
Fencer Intel
high 7.1

CVE-2018-12684 json

Out-of-bounds Read in the send_ssi_file function in civetweb.c in CivetWeb through 1.10 allows attackers to cause a Denial of Service or In…

published 8y ago modified 4mo ago also EUVD-2018-4637

cvss
7.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

Out-of-bounds Read in the send_ssi_file function in civetweb.c in CivetWeb through 1.10 allows attackers to cause a Denial of Service or Information Disclosure via a crafted SSI file.

Patch / fix

Is CVE-2018-12684 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2018-12684 updated cvss 5.4

civetweb: Out-of-bounds read in civetweb.c:send_ssi_file() allows attackers to cause denial of service or information disclosure

  • Red Hat Ceph Storage 1.3 ceph
    affected: no fix planned “Will not fix”
  • Red Hat Ceph Storage 2 ceph, librbd1, librgw2, ceph-mds, ceph-mon, ceph-osd, +12 more
    affected: no fix available
  • Red Hat Ceph Storage 3 ceph, librbd1, librgw2, ceph-mds, ceph-mgr, ceph-mon, +15 more
    affected: no fix planned “Will not fix”

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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.1 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P

Classification

Weakness
  • CWE-125 Out-of-bounds Read
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.