CVE-2010-3852 json
The default configuration of Luci 0.22.4 and earlier in Red Hat Conga uses "[INSERT SECRET HERE]" as its secret key for cookies, which make…
published 16y ago modified 4mo ago also EUVD-2010-3831
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
The default configuration of Luci 0.22.4 and earlier in Red Hat Conga uses "[INSERT SECRET HERE]" as its secret key for cookies, which makes it easier for remote attackers to bypass repoze.who authentication via a forged ticket cookie.
Is CVE-2010-3852 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-3852 updated cvss 4.0
Luci: Authentication bypass via fake ticket cookie
-
Red Hat Enterprise Linux 6 luciaffected: no fix available
-
Red Hat Enterprise Linux 5 conganot 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
2.00% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
lists.fedoraproject.org
/pipermail/package-announce/2010-November/050244.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2010-November/050309.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2010-November/050246.html
vendor-advisory
-
secunia.com
/advisories/42123
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2010/2873
vdb-entry, vendor-advisory
-
secunia.com
/advisories/42113
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2010/2900
vdb-entry
-
securityfocus.com
/bid/44611
vdb-entry
- bugzilla.redhat.com /show_bug.cgi?id=626504
-
osvdb.org
/69015
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/62980
vdb-entry
- git.fedorahosted.org /git/?p=luci.git%3Ba=commit%3Bh=9e0bbf0c5faa198379d945474f7d55da5031cacf
Sources
- CVE List CVE-2010-3852
- NVD CVE-2010-3852
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.