dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-28058

HIGH · 7.5 CVSS v3.1 Published 2024-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
In RSA NetWitness (NW) Platform before 12.5.1, even when an administrator revokes the access of a specific user with an active session, an internal threat actor could impersonate the revoked user and gain unauthorized access to sensitive data.

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

This is a session management vulnerability in RSA NetWitness Platform where user session tokens remain valid even after an administrator revokes the user's access. An internal threat actor with network access can intercept or reuse a session token from a revoked user to impersonate that user and access sensitive data.

MitigationUpgrade to RSA NetWitness Platform version 12.5.1 or later which properly invalidates all active sessions upon user access revocation. Review recent audit logs for any unauthorized access using sessions of recently revoked users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed RSA NetWitness Platform version
    Access the NetWitness web interface and navigate to Administration > System > Updates, or run the command 'nwversion' from the server CLI to retrieve the exact version number
    Affected if The installed version is earlier than 12.5.1 (the version that contains the fix)
  2. Review user access revocation audit logs
    In NetWitness, go to Investigate > Logs and filter for events containing 'revoke' or 'disable user' combined with 'session'. Alternatively, search in the raw logs for event.type='user' and action='revoke'
    Affected if Audit logs show users were recently revoked but no corresponding session invalidation events are recorded
  3. Identify active sessions for disabled or revoked users
    Query the session management database or use the NetWitness API endpoint '/rsaserv/rsaserv/session' to list active sessions, then cross-reference with the list of disabled/revoked user accounts
    Affected if Any active session exists for a user account that has been marked as disabled or had access revoked
  4. Check session timeout configuration
    Navigate to Administration > Security > Users in the NetWitness UI and review the session timeout policy settings, or inspect the file /etc/netwitness/ua/persistence.xml for session timeout parameters
    Affected if Session timeout is configured to an unusually long duration (greater than 24 hours) or is set to never expire

A defender is affected if their RSA NetWitness Platform version is earlier than 12.5.1 AND there are active user sessions associated with accounts that have been revoked or disabled, indicating the session invalidation flaw is 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to RSA NetWitness Platform version 12.5.1 or later which properly invalidates all active sessions upon user access revocation. Review recent audit logs for any unauthorized access using sessions of recently revoked users.

Recommended fix High confidence

RSA NetWitness Platform 12.5.1

  1. Upgrade RSA NetWitness Platform to version 12.5.1 or later to remediate the session revocation bypass vulnerability.
  2. After upgrading, verify that user session revocation now properly terminates active sessions and prevents session impersonation.
  3. Review audit logs to check for any suspicious activity that may have occurred while the vulnerability was present.
  4. As a best practice, consider implementing additional session monitoring controls for sensitive data access.

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

Have this fixed 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 help mitigating

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-2024-28058 — 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-2024-28058 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