CVE-2021-35198
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 · uneditedNETSCOUT nGeniusONE 6.3.0 build 1004 and earlier allows Stored Cross-Site Scripting (XSS) in the Packet Analysis module.
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 confidenceNETSCOUT nGeniusONE versions 6.3.0 build 1004 and earlier contains a stored Cross-Site Scripting (XSS) vulnerability in the Packet Analysis module. This occurs when the application fails to properly sanitize user-supplied input before storing and displaying it, allowing malicious JavaScript code to be persistently embedded and executed in the browsers of other users who access the affected functionality.
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<= 6.3.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed nGeniusONE versionAccess the nGeniusONE administration interface or use the product's built-in version check (typically found in Help > About or System > Status). Look for the build number and compare it to 6.3.0 build 1004.Affected if The installed version is 6.3.0 or earlier, or the build number is 1004 or lower.
-
Confirm the Packet Analysis module is in useNavigate to the Packet Analysis module within the nGeniusONE web interface. Check if this feature is enabled and accessible to users through the dashboard or navigation menu.Affected if The Packet Analysis module is present and accessible to users who can input or upload data into it.
-
Verify user input is processed in Packet AnalysisReview the Packet Analysis functionality to identify where users can supply input, such as filter definitions, labels, or analysis parameters. Attempt to identify input fields that accept custom text.Affected if Users can enter custom text or data values that get stored and displayed back in the interface.
-
Inspect stored data for malicious contentExamine the application's database or stored configurations related to Packet Analysis. Look for any stored scripts or unusual HTML/JavaScript code in fields that accept user-supplied input.Affected if Unexpected script tags or JavaScript code is found stored in Packet Analysis-related data fields.
A user is affected if they run nGeniusONE version 6.3.0 or earlier and the Packet Analysis module is accessible to users who can input custom data that gets persistently stored and displayed.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied patches for nGeniusONE to address the vulnerability. Until patches are available, implement output encoding and input validation on all data fields within the Packet Analysis module to neutralize malicious script content.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35198 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-35198 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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