dbcve.org
SnapmanagerApplication · Netapp

CVE-2019-5507

MEDIUM · 5.5 CVSS v3.1 Published 2019-10-09
Fix available
A fix is available. Upgrade to 3.4.2 or later.
See remediation →
57/100
Remediation priority · Elevated
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
SnapManager for Oracle prior to version 3.4.2P1 are susceptible to a vulnerability which when successfully exploited could lead to disclosure of sensitive information.

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

SnapManager for Oracle versions prior to 3.4.2P1 contain an information disclosure vulnerability. The specific nature of the exposed sensitive information and the exact attack vector are not detailed in the available documentation, though the CVSS 5.5 score indicates network accessibility with some complexity or privileges required.

MitigationUpgrade SnapManager for Oracle to version 3.4.2P1 or later to remediate this vulnerability. If upgrade is not immediately feasible, restrict network access to the SnapManager interfaces and follow Oracle's security hardening guidelines for the product.

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
SnapmanagerApplication
Affected:< 3.4.2= 3.4.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm SnapManager for Oracle is installed
    Check the list of installed programs on the system or locate the SnapManager for Oracle installation directory
    Affected if The product is not present means the vulnerability does not apply
  2. Locate the installed version
    Access the SnapManager for Oracle interface and navigate to Help > About, or check the installation directory for version files or product documentation
    Affected if The exact version number is needed to determine exposure
  3. Compare version to affected range
    Compare your installed version to the affected ranges: versions prior to 3.4.2 and version 3.4.2 are affected; version 3.4.2P1 and later are not affected
    Affected if If the installed version is 3.4.2 or earlier, the environment is vulnerable

The environment is affected if SnapManager for Oracle version 3.4.2 or earlier is installed.

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 3.4.2 or later
Fixed in 3.4.2
Interim mitigation

Upgrade SnapManager for Oracle to version 3.4.2P1 or later to remediate this vulnerability. If upgrade is not immediately feasible, restrict network access to the SnapManager interfaces and follow Oracle's security hardening guidelines for the product.

Fix this in Snapmanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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