dbcve.org
NetwitnessApplication · Rsa

CVE-2022-47529

MEDIUM · 6.7 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 12.2 or later.
See remediation →
69/100
Remediation priority · Elevated
Public exploit 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
Insecure Win32 memory objects in Endpoint Windows Agents in RSA NetWitness Platform before 12.2 allow local and admin Windows user accounts to modify the endpoint agent service configuration: to either disable it completely or run user-supplied code or commands, thereby bypassing tamper-protection features via ACL modification.

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

A detailed technical summary for this CVE is being prepared.

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:< 12.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 12.2 or later
Fixed in 12.2
Recommended fix High confidence

12.2

  1. Verify current NetWitness Platform version via the NetWitness UI (System > Health > Version) or via the /opt/rsa/sa/bin/nwversion.sh script
  2. Review RSA NetWitness Platform 12.2 Release Notes for upgrade prerequisites and supported migration paths
  3. Ensure all prerequisite upgrades (such as database, middleware) are completed before upgrading the Endpoint Agents
  4. Take a full snapshot/backup of the NetWitness Platform infrastructure before initiating the upgrade
  5. Use the NetWitness Platform installer or orchestration tools to upgrade to version 12.2 or later
  6. After upgrade, verify Endpoint Agent service is running and tamper-protection features are active
  7. Confirm via ACL verification that the Endpoint Windows Agent service has the correct security permissions (only SYSTEM and Administrators should have write access)
Caveat Review 12.2 release notes for any deprecations or breaking changes specific to your deployment configuration; some legacy endpoint agent features may require migration

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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