# CVE-2013-4766: Eucalyptus Unauthorized Access to CC/NC Log Files

> Remote attackers can read log files from Eucalyptus Cluster or Node Controllers without authentication, exposing sensitive information.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f5hm-h272-2qwm

## What is CVE-2013-4766?

CVE-2013-4766 is a medium-severity vulnerability in n/a, published on 17 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-4766?

2 open source packages ship an affected version, including org.jclouds.api:eucalyptus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jclouds.api:eucalyptus` | Maven | All versions | 3.3.1 |
| `org.jclouds.api:eucalyptus` | Maven | All versions | 3.3.1 |

Products: Eucalyptus Eucalyptus.

## How do I fix CVE-2013-4766?

Upgrade org.jclouds.api:eucalyptus to 3.3.1 or later.

## Is CVE-2013-4766 being exploited?

There is no known exploitation of CVE-2013-4766 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-4767](https://insights.sbomify.com/CVE-2013-4767/): Unspecified vulnerability in Eucalyptus before 3.3.2 has unknown impact and attack vectors. (critical 10.0)
- [CVE-2016-8520](https://insights.sbomify.com/CVE-2016-8520/): Missing authorization in Helion Eucalyptus (high 8.8)
- [CVE-2016-8528](https://insights.sbomify.com/CVE-2016-8528/): Privilege escalation in Helion Eucalyptus (high 8.8)
- [CVE-2015-6861](https://insights.sbomify.com/CVE-2015-6861/): Auth bypass in n/a (high 7.5)
- [CVE-2012-3240](https://insights.sbomify.com/CVE-2012-3240/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4766 and fix it if it is affected.

What it is: CVE-2013-4766 is a medium-severity vulnerability in n/a, published on 17 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4766 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jclouds.api:eucalyptus (Maven): affected all versions; fixed in 3.3.1
- org.jclouds.api:eucalyptus (Maven): affected all versions; fixed in 3.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4766/ (Markdown: https://insights.sbomify.com/CVE-2013-4766/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4766
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4766
- OSV: https://osv.dev/vulnerability/CVE-2013-4766

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4766/
Summaries are generated and may contain mistakes; the official description above is the record.