CVE-2013-4766 json
Eucalyptus Unauthorized Access to CC/NC Log Files
published 13y ago modified 4mo ago also GHSA-f5hm-h272-2qwm , EUVD-2022-3694
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
The gather log service in Eucalyptus before 3.3.1 allows remote attackers to read log files via an unspecified request to the (1) Cluster Controller (CC) or (2) Node Controller (NC) component.
Patch / fix
- maven org.jclouds.api:eucalyptus 3.3.1
Is CVE-2013-4766 in your dependencies? 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-2013-4766 updated cvss 4.3
eucalyptus: Unauthorized Access to CC/NC Log Files
-
Red Hat All currently supported Red Hat productsnot 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.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jclouds.api:eucalyptus | <3.3.1 |
3.3.1 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
eucalyptus.com
/resources/security/advisories/esa-13
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2013-4766
advisory
-
github.com
/eucalyptus/eucalyptus
package
Sources
- CVE List CVE-2013-4766
- GitHub Advisory GHSA-f5hm-h272-2qwm
- NVD CVE-2013-4766
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.