dbcve.org
Avamar ServerApplication · Emc

CVE-2013-3274

HIGH · 9.0 CVSS v2.0 Published 2013-07-19
Fix available
A fix is available. Upgrade to after 6.1 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
EMC Avamar Server and Avamar Virtual Edition before 7.0 on Data Store Gen3, Gen4, and Gen4s platforms do not properly determine authorization for calls to Java RMI methods, which allows remote authenticated users to execute arbitrary code 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

EMC Avamar Server and Virtual Edition versions before 7.0 on Data Store Gen3/Gen4/Gen4s platforms fail to properly authorize Java RMI (Remote Method Invocation) method calls, allowing any authenticated remote user to invoke arbitrary RMI methods and execute code with the privileges of the RMI service.

MitigationUpgrade to Avamar version 7.0 or later. If immediate patching is not feasible, restrict network access to RMI ports and enforce strong authentication for all Avamar administrative interfaces.

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
Avamar ServerApplication
Affected:<= 6.1= 4.0= 4.1= 5.0= 6.0
Avamar Server Virtual EditionApplication
Affected:<= 6.1= 4.0= 4.1= 5.0= 6.0

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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 installed Avamar version
    Run the command to display the Avamar server version, typically via 'avamar --version' or by checking the installed package version through the system package manager
    Affected if The installed version is 6.1 or earlier, or matches 4.0, 4.1, 5.0, or 6.0 exactly (versions before 7.0 are affected)
  2. Confirm Data Store platform type
    Check the hardware model or platform specification of the Data Store appliance (Gen3, Gen4, or Gen4s) through system information commands or appliance management interface
    Affected if The platform is Data Store Gen3, Gen4, or Gen4s and the Avamar version is below 7.0
  3. Verify Java RMI service status
    Check if the Java RMI service is running and listening on network ports. This can be done by reviewing running services related to RMI or checking listening network ports (commonly port 1099 for RMI registry)
    Affected if The RMI service is running and exposed on network ports (the vulnerability requires RMI to be enabled for exploitation)

You are affected if your installed Avamar Server or Virtual Edition version is below 7.0 (specifically 6.1 or earlier, or versions 4.0, 4.1, 5.0, or 6.0) and the Java RMI service is enabled on a Data Store Gen3/Gen4/Gen4s platform.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.1
Interim mitigation

Upgrade to Avamar version 7.0 or later. If immediate patching is not feasible, restrict network access to RMI ports and enforce strong authentication for all Avamar administrative interfaces.

Recommended fix High confidence

Avamar Server / Avamar Virtual Edition 7.0 or later

  1. 1. Identify the current Avamar Server version by checking the management console or running: 'avmversion' or 'dpcli --version'
  2. 2. Plan the upgrade to Avamar version 7.0 or later (the first fixed release)
  3. 3. Perform a complete backup of all critical data and configuration settings
  4. 4. Review EMC Avamar 7.0 upgrade documentation for your specific Data Store platform (Gen3, Gen4, or Gen4s)
  5. 5. Execute the upgrade following EMC's prescribed upgrade procedure
  6. 6. After upgrade, verify the version is 7.0 or higher
  7. 7. Test that Java RMI authorization is properly enforced
Caveat Major version upgrade may require compatibility review of existing backup policies and integrated applications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avamar Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3274 — 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-3274 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