NgeniuspulseHardware / appliance · Netscout

CVE-2023-40302

CRITICAL · 9.1 CVSS v3.1 Published 2023-12-07
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 nGeniusPULSE 3.8 has Weak File Permissions Vulnerability

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 nGeniusPULSE 3.8 contains a weak file permissions vulnerability that allows unauthorized access to sensitive files or directories due to overly permissive access controls (e.g., world-readable or world-writable permissions). This can lead to confidentiality compromise, data exfiltration, or privilege escalation, as reflected by the critical CVSS score.

MitigationReview and correct file and directory permissions on the nGeniusPULSE installation to ensure proper ownership and restrictive mode bits (e.g., 640 for config files, 755 for executables), following the principle of least privilege.

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
NgeniuspulseHardware / appliance
Affected:= 3.8.0-0.2349.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm nGeniusPULSE installation
    Locate the nGeniusPULSE installation directory or identify the running nGeniusPULSE service on the system. Common methods include checking for the installation in standard directories or running 'ps' commands to find nGeniusPULSE processes.
    Affected if nGeniusPULSE is installed and the installation directory or process is found on the system.
  2. Verify the installed version
    Determine the installed version of nGeniusPULSE by querying the application or reading version information from the installation directory. Compare the discovered version against the affected range: 3.8.0-0.2349.0.
    Affected if The installed version matches exactly 3.8.0-0.2349.0.
  3. Check for world-readable permissions
    Use 'ls -la' or 'getfacl' commands on the nGeniusPULSE installation directory and its subdirectories to identify files or directories with permissions that allow read access to all users (e.g., mode 644, 755, or any permission ending in 4 or 5 for others/group).
    Affected if Sensitive files such as configuration files, credentials, or log files are found with world-readable permissions (mode settings that include 'r--r--r--' or similar for others).
  4. Check for world-writable permissions
    Use 'ls -la' or 'getfacl' commands on the nGeniusPULSE installation directory to identify files or directories with permissions that allow write access to all users (e.g., mode 666, 777, or any permission ending in 2, 3, 6, or 7 for others/group).
    Affected if Any files or directories within the nGeniusPULSE installation are found with world-writable permissions (mode settings that include '-w-rw-rw-' or 'dwxrwxrwx' for others).

A system is affected if nGeniusPULSE version 3.8.0-0.2349.0 is installed and the installation directory contains files or directories with world-readable or world-writable permissions, exposing sensitive data or allowing unauthorized modification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and correct file and directory permissions on the nGeniusPULSE installation to ensure proper ownership and restrictive mode bits (e.g., 640 for config files, 755 for executables), following the principle of least privilege.

Fix this in Ngeniuspulse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2023-40302 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