dbcve.org
Smarts Network Configuration ManagerApplication · Emc

CVE-2013-0935

HIGH · 9.3 CVSS v2.0 Published 2013-03-28
Fix available
A fix is available. Upgrade to after 9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Smarts Network Configuration Manager (NCM) before 9.2 does not require authentication for all Java RMI method calls, which allows remote attackers 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 · high confidence

EMC Smarts Network Configuration Manager (NCM) versions before 9.2 fail to enforce authentication on Java RMI method calls, allowing unauthenticated remote attackers to invoke arbitrary methods and execute arbitrary code on the affected system.

MitigationUpgrade to EMC Smarts NCM version 9.2 or later to remediate this vulnerability. If immediate upgrade is not feasible, network segmentation and firewall rules should be applied to restrict access to the RMI ports.

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
Smarts Network Configuration ManagerApplication
Affected:<= 9.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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/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 if EMC Smarts NCM is installed
    Check for the Smarts NCM installation directory, typically under C:\Program Files\EMC\Smarts\ or /opt/EMC/Smarts/. On Windows, also check the list of installed programs in Add/Remove Programs or Programs and Features.
    Affected if The software is found on the system.
  2. Determine the installed version
    Look for a version file or check the productAbout file within the Smarts NCM installation directory. On Windows, right-click the executable and select Properties > Details to view the version. The version may also be visible in the NCM web interface login page or help/about section.
    Affected if The version is 9.1 or earlier.
  3. Identify if Java RMI service is running
    Check running processes for java.exe or the specific Smarts NCM service process. Use command 'netstat -an | findstr 1099' (or the configured RMI port) to see if port 1099 or the RMI registry port is listening.
    Affected if The RMI port is open and listening for connections.
  4. Verify RMI authentication configuration
    Examine the Smarts NCM configuration files for RMI settings. Look in the conf directory for files containing 'rmi', 'authentication', or 'security' settings. Check if authentication enforcement is explicitly disabled or missing.
    Affected if Authentication is not enforced or RMI access control is disabled in the configuration.

The system is affected if EMC Smarts NCM version 9.1 or earlier is installed and the Java RMI service is exposed without proper authentication enforcement.

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 9.1
Interim mitigation

Upgrade to EMC Smarts NCM version 9.2 or later to remediate this vulnerability. If immediate upgrade is not feasible, network segmentation and firewall rules should be applied to restrict access to the RMI ports.

Recommended fix High confidence

9.2 or later

  1. 1. Identify current installation version of EMC Smarts Network Configuration Manager by checking the installed version in the product UI or via command line tools
  2. 2. Create a complete backup of the NCM database, configuration files, and any custom scripts or integrations
  3. 3. Schedule a maintenance window as upgrades may require system downtime
  4. 4. Download EMC Smarts NCM version 9.2 or later from EMC/VMware support portal (depending on current support ownership)
  5. 5. Review upgrade documentation and release notes for version 9.2 for any specific pre-upgrade requirements
  6. 6. Execute the upgrade installer following the documented procedure for your operating system
  7. 7. After upgrade completion, verify the Java RMI services are running and authentication is enforced
  8. 8. Test that all NCM functions (discovery, configuration backup, change management) work correctly post-upgrade
Caveat Review release notes for version 9.2 for any configuration or feature changes; typical upgrade risks include potential impacts to custom integrations or workflows

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

Fix this in Smarts Network Configuration Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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