dbcve.org
Vg 4c1a Lru FirmwareOperating system · Biges

CVE-2023-6919

HIGH · 7.5 CVSS v3.1 Published 2024-01-26
Fix available
A fix is available. Upgrade to 500.0003.r008.4011.c0012.b351.c or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Path Traversal: '/../filedir' vulnerability in Biges Safe Life Technologies Electronics Inc. VGuard allows Absolute Path Traversal. This issue affects VGuard: before V500.0003.R008.4011.C0012.B351.C.

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 · high confidence

VGuard contains a path traversal vulnerability allowing absolute path traversal via '/../filedir' sequences. Attackers can use this to escape the intended directory and access sensitive files outside the web root, potentially exposing configuration files, credentials, or other system files.

MitigationUpgrade VGuard to version V500.0003.R008.4011.C0012.B351.C or later. If upgrade is not immediately possible, implement strict input validation to reject path traversal sequences ('../') and restrict file access to intended directories.

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
Vg 4c1a Lru FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 4c1a Lrpu FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 255a Bf FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 255 Bv FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 255 Df FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 64c8rd Nvr FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 4c1e Nvr FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c
Vg 8c1e Nvr FirmwareOperating system
Affected:< 500.0003.r008.4011.c0012.b351.c

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify VGuard device model and firmware version
    Access the device web interface or check the device status page to find the exact model name and firmware version number. Look for firmware version strings like '500.0003.r008.4011.c0012.b351.c' or earlier.
    Affected if The firmware version is less than 500.0003.r008.4011.c0012.b351.c for any Biges Vg variant (4c1a Lru, 4c1a Lrpu, 255a Bf, 255 Bv, 255 Df, 64c8rd Nvr, 4c1e Nvr, 8c1e Nvr).
  2. Locate the VGuard file upload or download interface
    Check the web management interface for file export, backup, log download, or configuration export features. These are typical paths where path traversal may be exploitable.
    Affected if The device has a web-accessible file transfer or export feature that accepts file path parameters.
  3. Test for path traversal vulnerability
    If file path parameters are observable, attempt a request with '/../' sequences (e.g., a URL parameter containing '../../../etc/passwd' or similar). Observe whether the application returns files from outside the intended directory.
    Affected if The application returns files from unintended directories when path traversal sequences are provided.

You are affected if your VGuard firmware version is below 500.0003.r008.4011.c0012.b351.c AND the device exposes a web-accessible file access feature that accepts path parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 500.0003.r008.4011.c0012.b351.c or later
Fixed in 500.0003.r008.4011.c0012.b351.c
Interim mitigation

Upgrade VGuard to version V500.0003.R008.4011.C0012.B351.C or later. If upgrade is not immediately possible, implement strict input validation to reject path traversal sequences ('../') and restrict file access to intended directories.

Recommended fix High confidence

V500.0003.R008.4011.C0012.B351.C or later

  1. 1. Identify the specific VGuard device model from the affected list (Vg 4c1a Lru, Vg 4c1a Lrpu, Vg 255a Bf, Vg 255 Bv, Vg 255 Df, Vg 64c8rd Nvr, Vg 4c1e Nvr, or Vg 8c1e Nvr)
  2. 2. Access the device management interface or contact Biges Safe Life Technologies Electronics Inc. for the firmware update
  3. 3. Obtain firmware version V500.0003.R008.4011.C0012.B351.C or later from the vendor
  4. 4. Backup current device configuration before performing firmware upgrade
  5. 5. Apply the firmware upgrade following the vendor's documented upgrade procedure
  6. 6. Verify the device is running the fixed firmware version after upgrade
  7. 7. Test to confirm the path traversal vulnerability is no longer exploitable
Caveat Firmware upgrades may require device reconfiguration; review vendor release notes for any configuration changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vg 4c1a Lru Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6919 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6919 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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