CVE-2012-3359 json
Luci in Red Hat Conga stores the user's username and password in a Base64 encoded string in the __ac session cookie, which allows attackers…
published 2014-03-30 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-3336
- cvss
- 3.7
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Luci in Red Hat Conga stores the user's username and password in a Base64 encoded string in the __ac session cookie, which allows attackers to gain privileges by accessing this cookie. NOTE: this issue has been SPLIT due to different vulnerability types. Use CVE-2013-7347 for the incorrect enforcement of a user timeout.
Patch / fix
- conga RHEL 5 CLUSTER 0.12.2-64.el5
- luci RHEL 5 CLUSTER 0.12.2-64.el5
- ricci RHEL 5 CLUSTER 0.12.2-64.el5
red hat advisories RHSA-2013:0128
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-3359 updated cvss 3.7
conga: insecure handling of luci web interface sessions
-
Red Hat Enterprise Linux 5 congaaffected: no fix available
-
Red Hat Enterprise Linux Clustering (v. 5 server) luci 0.12.2-64.el5, conga 0.12.2-64.el5, ricci 0.12.2-64.el5fixed: vendor fix RHSA-2013:0128
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
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.7 | AV:L/AC:H/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
Sources
- CVE List CVE-2012-3359
- NVD CVE-2012-3359
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.