dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-32980

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
NETSCOUT nGeniusONE before 6.4.0 P11 b3245 has a Weak Sudo Configuration.

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

NETSCOUT nGeniusONE before version 6.4.0 P11 b3245 contains a weak sudo configuration vulnerability that allows unauthorized users to execute privileged commands, potentially leading to complete system compromise with root access.

MitigationUpgrade to NETSCOUT nGeniusONE version 6.4.0 P11 b3245 or later to obtain the patched sudo configuration. After upgrading, audit the sudoers configuration to ensure proper least-privilege enforcement.

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

CVSS:3.1/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 nGeniusONE version
    Run the command to display the nGeniusONE version (typically via CLI or web interface). On the appliance, you may use: cat /opt/netscout/version or check the web UI under System > About. Compare the version number and build to 6.4.0 P11 b3245.
    Affected if The installed version is lower than 6.4.0 P11 b3245, or the version cannot be determined and is presumed to be an earlier release.
  2. Locate and inspect the sudoers configuration
    Examine the sudoers file(s) used by the system. Check /etc/sudoers and any files in /etc/sudoers.d/ directory. Use the command: visudo -c or cat /etc/sudoers | grep -v '^#' | grep -v '^$' to list active rules.
    Affected if Any entries allow unprivileged users to run commands as root without proper restrictions, or the sudoers file is world-readable or has incorrect ownership.
  3. Check for NOPASSWD privilege escalation flags
    Search the sudoers configuration for NOPASSWD directives. Run: grep -r 'NOPASSWD' /etc/sudoers /etc/sudoers.d/ 2>/dev/null. Review each NOPASSWD rule to determine if it grants excessive privileges.
    Affected if NOPASSWD entries exist that allow any user or group to execute privileged commands without authentication.
  4. Identify overly permissive sudo rules
    Review all sudo rules for broad command execution rights. Look for rules that permit execution of /bin/bash, /bin/sh, /usr/bin/*, or allow access to all commands (ALL=(ALL) ALL). Use: grep 'ALL=' /etc/sudoers /etc/sudoers.d/* 2>/dev/null.
    Affected if Rules exist that grant unrestricted or overly broad command execution privileges to non-admin users or groups.

A system is affected if it runs nGeniusONE version lower than 6.4.0 P11 b3245 AND contains weak, permissive, or misconfigured sudoers entries that allow unauthorized privileged access.

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 NETSCOUT nGeniusONE version 6.4.0 P11 b3245 or later to obtain the patched sudo configuration. After upgrading, audit the sudoers configuration to ensure proper least-privilege enforcement.

Recommended fix High confidence

6.4.0 P11 b3245 or later (latest stable release)

  1. Check the current nGeniusONE version via the console (Help > About) or CLI command 'show version'.
  2. If the version is earlier than 6.4.0 P11 b3245, plan a maintenance window.
  3. Back up the current system configuration using the built‑in backup function or export settings.
  4. Download the 6.4.0 P11 b3245 (or later) update package from the NETSCOUT support portal.
  5. Apply the upgrade following the vendor’s documented upgrade procedure (e.g., using the software update wizard or CLI command).
  6. After the upgrade completes, verify the new version is 6.4.0 P11 b3245 or later.
  7. Confirm the weak sudo configuration has been hardened by reviewing the sudoers file or security settings, and re‑apply any custom sudo rules if needed.
Caveat Custom sudo rules may need to be reviewed and reapplied after the upgrade.

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

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

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-2025-32980 — 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-2025-32980 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