dbcve.org
Eucalyptus Management ConsoleApplication · Eucalyptus

CVE-2013-4770

MEDIUM · 6.1 CVSS v3.1 Published 2020-01-27
Fix available
A fix is available. Upgrade to 4.0.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting (XSS) vulnerability in Eucalyptus Management Console (EMC) 4.0.x before 4.0.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-site scripting (XSS) vulnerability in Eucalyptus Management Console (EMC) versions 4.0.x before 4.0.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

MitigationUpgrade Eucalyptus Management Console to version 4.0.1 or later to remediate this XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Eucalyptus Management ConsoleApplication
Affected:>= 4.0.0, < 4.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Eucalyptus Management Console installation
    Locate the EMC installation directory or check installed packages using the system package manager (e.g., rpm, dpkg, or pip list) for eucalyptus-console or eucalyptus-admin packages
    Affected if The package is found but version cannot be determined
  2. Determine installed EMC version
    Run 'eucalyptus-console --version' or check the package version via the package manager (e.g., 'rpm -qi eucalyptus-console' or 'dpkg -l eucalyptus-console')
    Affected if Version command fails or package is not found
  3. Compare version to affected range
    Check if the installed version starts with 4.0.0 (e.g., 4.0.0, 4.0.0-x) and is less than 4.0.1
    Affected if Version is 4.0.0.x where x is any suffix, or version begins with 4.0.0 and is below 4.0.1
  4. Verify web console is accessible
    Confirm the EMC web interface is enabled and accessible (check if eucalyptus-console service is running and port 8888 or 443 is listening)
    Affected if The console is running and version is in the affected range

The environment is affected if Eucalyptus Management Console version is 4.0.0.x (any 4.0.0 release) and the web console is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 4.0.1 or later
Fixed in 4.0.1
Interim mitigation

Upgrade Eucalyptus Management Console to version 4.0.1 or later to remediate this XSS vulnerability.

Fix this in Eucalyptus Management Console Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-4770 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data