CVE-2023-33477
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 · uneditedIn Harmonic NSG 9000-6G devices, an authenticated remote user can obtain source code by directly requesting a special path.
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 confidenceThis is a path traversal vulnerability in Harmonic NSG 9000-6G devices where an authenticated remote user can obtain source code by directly requesting a special path. The vulnerability allows accessing sensitive source code files through improper path validation.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device management interface or check the system information page to confirm the exact model is Harmonic NSG 9000-6GAffected if The device is a Harmonic NSG 9000-6G unit
-
Confirm firmware versionLocate the firmware version information in the device web interface under System, About, or Diagnostics sectionsAffected if Any firmware version is installed (all versions are affected)
-
Verify remote management is enabledCheck the device network configuration to determine if the web-based management interface is accessible remotely (not limited to localhost or console only)Affected if Remote web management or API access is enabled and accessible over the network
-
Confirm authentication is requiredTest whether the management interface requires login credentials or verify that authentication is enforced in the security settingsAffected if Remote authentication is configured (the vulnerability requires an authenticated session)
-
Test for path traversal accessSend an HTTP request to the web interface attempting to access source code files using path traversal patterns (such as ../../etc/passwd or similar paths relative to the web root). If the device returns source code content or sensitive file contents, the vulnerability is present.Affected if The device returns source code or sensitive file contents in response to path traversal requests
The environment is affected if it is a Harmonic NSG 9000-6G device with remote web management enabled and accessible using valid credentials, as the path traversal flaw allows authenticated users to access source code files outside the intended web directory.
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 or updates for the NSG 9000-6G device. If no patch is available, restrict administrative access to trusted IPs and implement strong authentication mechanisms to limit exposure.
- 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-2023-33477 — 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-33477 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