How severe is CVE-2013-4766?

No CVSS score has been assigned to CVE-2013-4766 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4766?

CVE-2013-4766 affects the following packages: org.jclouds.api:eucalyptus (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4766?

Update org.jclouds.api:eucalyptus to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4766 is resolved across your whole dependency graph.

How do I detect CVE-2013-4766 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jclouds.api:eucalyptus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-4766 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-4766 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-4766 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-4766?

CVE-2013-4766 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 67th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-4766?

CVE-2013-4766 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-4766 published, and has it been updated?

CVE-2013-4766 was published on May 17, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-4766 — eucalyptus

CVE-2013-4766 is a Information Exposure vulnerability in org.jclouds.api:eucalyptus. A fix is available for org.jclouds.api:eucalyptus — see the affected versions and patch details below.

Eucalyptus Unauthorized Access to CC/NC Log Files

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.jclouds.api:eucalyptus

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jclouds.api:eucalyptus`	all versions	3.3.1`org.jclouds.api:eucalyptus:3.3.1`

Affected Products

1 product · 23 configurations

Application

eucalyptuseucalyptus

≤ 3.3.0

22 versions

1.01.11.21.31.41.5.11.5.21.61.6.22.02.0.02.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jclouds.api:eucalyptus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jclouds.api:eucalyptus to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4766 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2013-4766 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works