CVE-2023-6118
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 · uneditedPath Traversal: '/../filedir' vulnerability in Neutron IP Camera allows Absolute Path Traversal. This issue affects IP Camera: before b1130.1.0.1.
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 confidencePath traversal vulnerability in Neutron IP Camera firmware allows attackers to use '../' sequences to traverse directories and access files outside the web root, potentially exposing system files, credentials, and configuration data.
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< b1130.1.0.1< b1130.1.0.1< b1130.1.0.1< b1130.1.0.1< b1130.1.0.1< b1130.1.0.1< b1130.1.0.1< b1130.1.0.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Neutron camera modelAccess the camera web interface or check the device label to confirm the exact model number (e.g., Neu Ipb210, Ntl Pt 06wod 3mp, Neu Ipb410, Ntl Bc 01w, Neu Ipbm211, Ntl Pt 09 Wos 3mp, Neu Ipbm411, Ntl Pt 10 4gwos 3mp)Affected if The model matches one of the eight affected product names listed in the CVE
-
Check the installed firmware versionLog into the camera web interface and navigate to the System or Settings menu to view the firmware version, or use the manufacturer's discovery tool or API if availableAffected if The firmware version is present and lower than b1130.1.0.1 (for example, b1129.x.x.x or any build prior to b1130.1.0.1)
-
Verify the web service is enabledConfirm the camera HTTP/HTTPS web interface is active by attempting to access the camera IP address in a browser or running a port scan for ports 80 or 443Affected if The web interface is accessible and the camera is on the network
-
Confirm network accessibility of the management interfaceCheck if the camera web port is exposed to untrusted networks or the internet by reviewing firewall rules, port forwarding configurations, or performing an external port scanAffected if The camera management interface is reachable from untrusted networks without network segmentation or access controls
A user is affected if they have one of the eight Neutron camera models listed with firmware version older than b1130.1.0.1 and the web interface is accessible, allowing path traversal via '../' sequences to escape the web root.
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.
dbcve · scopedApply vendor firmware update b1130.1.0.1 or later to patch the path validation vulnerability; as interim control, restrict network access to camera management interfaces.
b1130.1.0.1
- 1. Identify the exact Neutron IP Camera model from the affected list: Ipb210 28, Ipb410 28, Ipbm211, Ipbm411, Ntl Pt 06wod 3mp, Ntl Pt 09 Wos 3mp, Ntl Pt 10 4gwos 3mp, or Ntl Bc 01w
- 2. Access the camera's web management interface or use the vendor's configuration tool
- 3. Navigate to the firmware/version information section to confirm current firmware version is below b1130.1.0.1
- 4. Obtain the fixed firmware version b1130.1.0.1 from the official Neutron vendor (manufacturer support or download portal)
- 5. Backup current camera configuration if the interface provides export functionality
- 6. Upload and apply firmware b1130.1.0.1 using the camera's firmware upgrade function
- 7. After reboot, verify the new firmware version is b1130.1.0.1 or higher
- 8. Restore configuration if previously backed up
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6118 — 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-6118 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