dbcve.org
Vipr SrmApplication · Emc

CVE-2016-0922

CRITICAL · 9.8 CVSS v3.0 Published 2016-09-18
Fix available
A fix is available. Upgrade to after 3.7.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 ViPR SRM before 3.7.2 does not restrict the number of password-authentication attempts, which makes it easier for remote attackers to obtain access via a brute-force guessing attack.

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 ViPR SRM versions prior to 3.7.2 lack account lockout mechanisms or rate limiting on the authentication interface, allowing remote attackers to make unlimited password guessing attempts. This enables credential brute-force attacks where attackers systematically try password combinations until they gain unauthorized access to the system.

MitigationUpgrade EMC ViPR SRM to version 3.7.2 or later, which implements authentication attempt restrictions. Consider implementing additional controls such as IP-based rate limiting at the network perimeter while planning the upgrade.

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
Vipr SrmApplication
Affected:<= 3.7.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 EMC ViPR SRM version
    Locate and determine the installed version of EMC ViPR SRM in your environment. This is typically available through the product's web interface (Help/About), command-line interface, or installation records.
    Affected if The installed version is 3.7.1 or earlier (any version prior to 3.7.2)
  2. Assess authentication interface exposure
    Determine whether the ViPR SRM authentication interface is network-accessible. Identify the port used (commonly 8443 for the web UI) and verify if it is reachable from external or untrusted networks.
    Affected if The authentication interface is exposed to network segments beyond the trusted internal network
  3. Verify account lockout configuration
    Check the authentication security settings within ViPR SRM for account lockout policies (e.g., maximum failed attempts before lockout) and rate limiting controls (e.g., restrictions on login attempts per time window).
    Affected if No account lockout mechanism or rate limiting is configured on the authentication interface

You are affected if running ViPR SRM version 3.7.1 or earlier with the authentication interface accessible and no lockout/rate limiting controls present.

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

Upgrade EMC ViPR SRM to version 3.7.2 or later, which implements authentication attempt restrictions. Consider implementing additional controls such as IP-based rate limiting at the network perimeter while planning the upgrade.

Recommended fix High confidence

3.7.2

  1. Check the current ViPR SRM version in the administration console or system information
  2. Download ViPR SRM version 3.7.2 from the EMC/VMware support portal (requires valid support account)
  3. Review the official upgrade guide and release notes for 3.7.2 for any prerequisites or pre-upgrade requirements
  4. Create a complete backup of the ViPR SRM database and configuration
  5. Schedule a maintenance window as the upgrade may require service downtime
  6. Run the upgrade installer following the documented upgrade procedure
  7. After upgrade completes, verify the version shows 3.7.2 or later
  8. Confirm that login brute-force protection is now enforced by testing with multiple failed authentication attempts
Caveat Review 3.7.2 release notes for any feature deprecations or configuration changes before upgrading

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

Fix this in Vipr Srm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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