NgeniusoneApplication · Netscout

CVE-2021-35203

MEDIUM · 5.7 CVSS v3.1 Published 2021-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 Systems nGeniusONE 6.3.0 build 1196 allows Arbitrary File Read operations via the FDSQueryService endpoint.

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

nGeniusONE 6.3.0 build 1196 contains an arbitrary file read vulnerability in the FDSQueryService endpoint. An attacker can exploit this to read sensitive files from the underlying filesystem, potentially exposing configuration files, credentials, or other system data.

MitigationApply the vendor-supplied patch for CVE-2021-35203 or upgrade to a patched version. If no patch is immediately available, restrict network access to the FDSQueryService endpoint and implement additional authentication controls.

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
NgeniusoneApplication
Affected:= 6.3.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Confirm nGeniusONE installation
    Locate the nGeniusONE installation directory, typically under C:\Program Files\NETSCOUT\nGeniusONE or /opt/ngeniusone, and verify the software is present.
    Affected if The nGeniusONE software is found on the system.
  2. Identify installed version
    Check the version information in the nGeniusONE installation by examining version.info, about dialog in the management console, or using the nGeniusONE command-line version query if available.
    Affected if The installed version is exactly 6.3.0 build 1196.
  3. Verify FDSQueryService endpoint accessibility
    Attempt to access the FDSQueryService endpoint via HTTP/HTTPS on the nGeniusONE management interface port (typically 443 or 8080). The endpoint path is typically /FDSQueryService or similar. Use a web browser or curl to test connectivity.
    Affected if The FDSQueryService endpoint responds and is reachable from the network.
  4. Review access logs for suspicious file read patterns
    Examine nGeniusONE server logs, typically found in the logs directory under the installation path, for unusual or unauthorized requests to FDSQueryService that may indicate file path traversal attempts.
    Affected if Logs show requests to FDSQueryService with path traversal patterns (e.g., ../../) or access to sensitive system files.

You are affected if nGeniusONE version 6.3.0 build 1196 is installed and the FDSQueryService endpoint is network-accessible.

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

Apply the vendor-supplied patch for CVE-2021-35203 or upgrade to a patched version. If no patch is immediately available, restrict network access to the FDSQueryService endpoint and implement additional authentication controls.

Fix this in Ngeniusone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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