CVE-2013-4766: Infoleak
Published Sep 17, 2013
·Updated
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 Software
24 affected componentsFixes available
maven/org.jclouds.api:eucalyptus<3.3.1
3.3.1
Eucalyptus Eucalyptus<=3.3.0
Eucalyptus Eucalyptus=1.0
Eucalyptus Eucalyptus=1.1
Eucalyptus Eucalyptus=1.2
Eucalyptus Eucalyptus=1.3
Eucalyptus Eucalyptus=1.4
Eucalyptus Eucalyptus=1.5.1
Eucalyptus Eucalyptus=1.5.2
Eucalyptus Eucalyptus=1.6
Eucalyptus Eucalyptus=1.6.2
Eucalyptus Eucalyptus=2.0
Eucalyptus Eucalyptus=2.0.0
Eucalyptus Eucalyptus=2.0.1
Eucalyptus Eucalyptus=2.0.2
Eucalyptus Eucalyptus=2.0.3
Eucalyptus Eucalyptus=3.0
Eucalyptus Eucalyptus=3.0.1
Eucalyptus Eucalyptus=3.1.0
Eucalyptus Eucalyptus=3.1.1
Eucalyptus Eucalyptus=3.1.2
Eucalyptus Eucalyptus=3.2.0
Eucalyptus Eucalyptus=3.2.1
Eucalyptus Eucalyptus=3.2.2
Event History
Sep 17, 2013
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
May 17, 2022
Advisory Published
05:04 AM
Frequently Asked Questions
1
What is the severity of CVE-2013-4766?
CVE-2013-4766 is classified with a high severity level due to the potential for unauthorized remote access to sensitive log files.
2
How do I fix CVE-2013-4766?
To fix CVE-2013-4766, upgrade Eucalyptus to version 3.3.1 or later.
3
What products are affected by CVE-2013-4766?
CVE-2013-4766 affects various versions of Eucalyptus software prior to 3.3.1.
4
Can CVE-2013-4766 lead to data breaches?
Yes, CVE-2013-4766 can potentially lead to data breaches as it allows remote attackers to read sensitive log files.
5
Is there any workaround for CVE-2013-4766 before applying a patch?
There are no known effective workarounds for CVE-2013-4766; upgrading is recommended as the only solution.