dbcve.org
NetwitnessApplication · Rsa

CVE-2019-3725

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-15
Fix available
A fix is available. Upgrade to 10.6.6.1 / 11.2.1.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
RSA Netwitness Platform versions prior to 11.2.1.1 and RSA Security Analytics versions prior to 10.6.6.1 are vulnerable to a Command Injection vulnerability due to missing input validation in the product. A remote unauthenticated malicious user could exploit this vulnerability to execute arbitrary commands on the server.

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

RSA Netwitness Platform and RSA Security Analytics contain a pre-authentication command injection vulnerability due to missing input validation. A remote unauthenticated attacker can execute arbitrary operating system commands on the affected server by injecting malicious input into vulnerable parameters.

MitigationUpgrade RSA Netwitness Platform to version 11.2.1.1 or later, and RSA Security Analytics to version 10.6.6.1 or later, to remediate this 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
NetwitnessApplication
Affected:< 11.2.1.1
Security AnalyticsApplication
Affected:< 10.6.6.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 installed RSA product
    Determine whether RSA Netwitness Platform or RSA Security Analytics is deployed in your environment. Check product documentation, installation records, or look for common installation directories such as /rsa or /netwitness.
    Affected if Either RSA Netwitness or RSA Security Analytics is installed
  2. Determine installed version of RSA Netwitness
    If RSA Netwitness is installed, check the version by accessing the Admin UI and navigating to System > Status, or check the version file in the installation directory. The version is typically displayed in the login page footer or in the /opt/rsa/sa/etc/version file if available.
    Affected if Version is lower than 11.2.1.1
  3. Determine installed version of RSA Security Analytics
    If RSA Security Analytics is installed, check the version via the Admin interface under System > License, or look for version information in the installation logs or configuration files.
    Affected if Version is lower than 10.6.6.1
  4. Verify network exposure of the web interface
    Determine if the RSA web interface (typically ports 443, 8443, or 8080) is accessible from untrusted networks. Review firewall rules and access control lists to confirm whether the login page is exposed to the internet or untrusted internal segments.
    Affected if The web interface is accessible from untrusted networks without proper network segmentation

Your environment is affected if either RSA Netwitness version below 11.2.1.1 or RSA Security Analytics version below 10.6.6.1 is installed and its web interface is network-accessible to untrusted users.

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 10.6.6.1 / 11.2.1.1 or later
Fixed in 10.6.6.111.2.1.1
Interim mitigation

Upgrade RSA Netwitness Platform to version 11.2.1.1 or later, and RSA Security Analytics to version 10.6.6.1 or later, to remediate this vulnerability.

Recommended fix High confidence

RSA Netwitness Platform 11.2.1.1 or RSA Security Analytics 10.6.6.1

  1. Back up all Netwitness/Security Analytics configurations, databases, and critical data before upgrading
  2. Download RSA Netwitness Platform version 11.2.1.1 or RSA Security Analytics version 10.6.6.1 from the official RSA download portal (requires valid support account)
  3. Review the official RSA upgrade documentation for your specific product version
  4. Apply the upgrade following the documented upgrade procedure for your deployment type
  5. After upgrade completion, verify all services are running correctly
  6. Confirm the version numbers reflect the upgraded releases (11.2.1.1 for Netwitness, 10.6.6.1 for Security Analytics)

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

Fix this in Netwitness Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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