CVE-2023-35069
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Bullwark allows Path Traversal. This issue affects Bullwark: before BLW-2016E-960H.
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 Bullwark video surveillance/NVR devices allows remote attackers to access arbitrary files on the system by manipulating file path inputs in HTTP requests. With a CVSS 7.5 (network-exploitable, no authentication required), this could expose sensitive system files, configuration data, credentials, or stored video footage.
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< blw-2016e-960hCVSS 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 Bullwark Momentum Series deviceCheck the device label, web interface banner, or SNMP inventory for 'Bullwark' and 'Momentum Series' product identificationAffected if Device is not a Bullwark Momentum Series NVR, then not affected
-
Check firmware versionAccess the device web interface (usually via HTTP on ports 80/8080), navigate to System > Firmware/About, or query the device's API endpoint for version information. Compare the version string to 'blw-2016e-960h'Affected if Firmware version is lower than blw-2016e-960h (e.g., older builds, unversioned, or any version missing the fix)
-
Verify HTTP management interface is accessibleAttempt to reach the device's IP address on HTTP port 80 or 8080 from the network perspective you are testing. Check if the login page or API respondsAffected if The HTTP management interface responds to network requests, indicating the attack surface is exposed
The environment is affected if it is a Bullwark Momentum Series NVR device running firmware version lower than blw-2016e-960H with its HTTP interface network-accessible.
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 to version BLW-2016E-960H or later; if unavailable, restrict network access to the device's management interface and implement WAF rules to filter directory traversal sequences (../, ..\) from requests.
BLW-2016E-960H or later
- 1. Identify the current firmware version of the Bullwark Momentum Series device
- 2. Download the latest firmware update (BLW-2016E-960H or later) from the official Bullwark vendor
- 3. Consult the vendor's firmware upgrade documentation for specific procedures
- 4. Backup current device configuration before performing the upgrade
- 5. Apply the firmware update following vendor instructions
- 6. Verify the device is functioning correctly after the upgrade
- 7. Confirm the firmware version has been updated to BLW-2016E-960H or later
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-35069 — 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-35069 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