dbcve.org
Rsa NetwitnessApplication · Emc

CVE-2018-11061

CRITICAL · 9.1 CVSS v3.0 Published 2018-08-24
Fix available
A fix is available. Upgrade to 10.6.6 / 11.1.0.2 or later.
See remediation →
97/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
RSA NetWitness Platform versions prior to 11.1.0.2 and RSA Security Analytics versions prior to 10.6.6 are vulnerable to a server-side template injection vulnerability due to insecure configuration of the template engine used in the product. A remote authenticated malicious RSA NetWitness Server user with an Admin or Operator role could exploit this vulnerability to execute arbitrary commands on the server with root privileges.

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

Server-side template injection vulnerability in RSA NetWitness Platform and RSA Security Analytics due to insecure template engine configuration. Authenticated users with Admin or Operator roles can execute arbitrary commands with root privileges.

MitigationUpgrade to RSA NetWitness Platform 11.1.0.2+ or RSA Security Analytics 10.6.6+ to patch the insecure template engine configuration.

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
Rsa NetwitnessApplication
Affected:< 11.1.0.2
Rsa Security AnalyticsApplication
Affected:< 10.6.6

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/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 the installed RSA product
    Determine whether your system is running RSA NetWitness Platform or RSA Security Analytics by checking the product name in the system UI or using the command 'rpm -qa | grep -i rsa' or 'dpkg -l | grep -i rsa' to list installed RSA packages.
    Affected if The system runs either RSA NetWitness Platform or RSA Security Analytics and the version is below the fixed releases.
  2. Check the installed version of RSA NetWitness Platform
    Run the command 'rpm -qa | grep netwitness' or check the version in the Administration > System page of the web interface.
    Affected if The version is lower than 11.1.0.2.
  3. Check the installed version of RSA Security Analytics
    Run the command 'rpm -qa | grep security-analytics' or check the version in the Administration > System page of the web interface.
    Affected if The version is lower than 10.6.6.
  4. Verify the template engine configuration
    Examine the template engine configuration files or settings in the RSA web interface under Administration > System Configuration > Template settings. Look for configurations that allow user-supplied input to be processed by the template engine.
    Affected if The template engine is enabled and accepts user input without proper sanitization, allowing server-side template injection.
  5. Check for admin or operator role assignments
    Review user role assignments in Administration > Users > Users and Roles to determine which accounts have Admin or Operator privileges.
    Affected if There are user accounts with Admin or Operator roles, and those accounts could potentially exploit the template injection vulnerability to execute commands as root.

Your environment is affected if it runs RSA NetWitness Platform below version 11.1.0.2 or RSA Security Analytics below version 10.6.6, and the template engine feature is enabled with user input processing capability accessible to Admin or Operator role 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 / 11.1.0.2 or later
Fixed in 10.6.611.1.0.2
Interim mitigation

Upgrade to RSA NetWitness Platform 11.1.0.2+ or RSA Security Analytics 10.6.6+ to patch the insecure template engine configuration.

Recommended fix High confidence

RSA NetWitness Platform 11.1.0.2 or RSA Security Analytics 10.6.6

  1. 1. Backup all RSA NetWitness/Security Analytics configurations and data before initiating any upgrade.
  2. 2. Download the fixed version: RSA NetWitness Platform 11.1.0.2 or RSA Security Analytics 10.6.6 from the official RSA download portal.
  3. 3. Follow the official RSA upgrade documentation for your specific product to apply the upgrade.
  4. 4. After upgrade completion, verify the version number matches the fixed release.
  5. 5. Confirm the template engine configuration has been secured by the patch.
  6. 6. Test that Admin/Operator role permissions are properly enforced.

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

Fix this in Rsa Netwitness Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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