CVE-2023-33335
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 · uneditedCross Site Scripting (XSS) in Sophos Sophos iView (The EOL was December 31st 2020) in grpname parameter that allows arbitrary script to be executed.
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 confidenceA stored or reflected Cross Site Scripting (XSS) vulnerability exists in the grpname parameter of Sophos iView. Attackers can inject malicious JavaScript code that executes in the browser sessions of users who interact with the affected parameter, potentially stealing session cookies or performing actions on behalf of authenticated users.
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 dataall versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 if Sophos iView is installedCheck for Sophos iView installation by looking for the application in your inventory, scanning network services on typical ports (port 8443, 443, or as configured), or checking installed programs on servers where it may have been deployed.Affected if Sophos iView is found running in the environment
-
Confirm the installed versionAccess the Sophos iView admin interface or check the software installation directory for version information. The application typically displays version details on the login page or in the about/system info section.Affected if Any version of Sophos iView is running (all versions are affected)
-
Verify grpname parameter is accessibleCheck if the web interface is exposed by attempting to access the login page or common paths. The grpname parameter is typically used in group management or authentication-related functionality.Affected if The Sophos iView web interface is accessible and the grpname parameter exists in the application's request handling
-
Test for XSS in grpname parameterIf you have authorized access, send a benign test payload to the grpname parameter (for example, a non-harmful string like <script>alert(1)</script> as part of a form submission or URL parameter) and observe if it is reflected back in the response without proper sanitization.Affected if The grpname parameter reflects unsanitized input back to the user, indicating the XSS vulnerability is present
If Sophos iView is running and the grpname parameter is accessible without input sanitization, the environment is affected by this XSS vulnerability.
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 dataSince Sophos iView reached end-of-life on December 31, 2020 with no official patches available, organizations should deploy Web Application Firewall (WAF) rules to sanitize or block malicious input to the grpname parameter, or migrate to a supported Sophos product.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-33335 — 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-2023-33335 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