Skip to content
Fencer Intel
medium 5.0

CVE-2013-6496 json

Red Hat Conga 0.12.2 allows remote attackers to obtain sensitive information via a crafted request to the (1) homebase, (2) cluster, (3) st…

published 12y ago modified 4mo ago also EUVD-2013-6299

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

Summary

Red Hat Conga 0.12.2 allows remote attackers to obtain sensitive information via a crafted request to the (1) homebase, (2) cluster, (3) storage, (4) portal_skins/custom, or (5) logs Luci extension.

Patch / fix

  • conga RHEL 5 CLUSTER 0.12.2-81.el5
  • luci RHEL 5 CLUSTER 0.12.2-81.el5
  • ricci RHEL 5 CLUSTER 0.12.2-81.el5

red hat advisories RHSA-2014:1194

Is CVE-2013-6496 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-2013-6496 updated cvss 5.0

conga: Multiple information leak flaws in various luci site extensions

  • Red Hat Enterprise Linux 5 conga
    affected: no fix available
  • Red Hat Enterprise Linux Clustering (v. 5 server) luci 0.12.2-81.el5, conga 0.12.2-81.el5, ricci 0.12.2-81.el5
    fixed: vendor fix RHSA-2014:1194
  • Red Hat Enterprise Linux 6 luci
    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

1.78% chance of exploitation in the next 30 days, higher than 78% 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:P/I:N/A:N

Classification

Weakness
  • 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.