dbcve.org
1704 Wgl FirmwareOperating system · Bdcom

CVE-2023-0659

HIGH · 7.5 CVSS v3.1 Published 2023-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability was found in BDCOM 1704-WGL 2.0.6314. It has been classified as critical. This affects an unknown part of the file /param.file.tgz of the component Backup File Handler. The manipulation leads to information disclosure. It is possible to initiate the attack remotely. The identifier VDB-220101 was assigned to this vulnerability.

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 confidence

The BDCOM 1704-WGL device firmware 2.0.6314 contains an information disclosure vulnerability in its Backup File Handler component. Attackers can remotely access the /param.file.tgz backup file, which typically contains device configuration data including network settings, credentials, and other sensitive parameters. The vulnerability stems from improper access controls on the backup file download functionality.

MitigationRestrict network access to the device's management interface, implement proper authentication for backup file downloads, and contact BDCOM for firmware patches. As a compensating control, monitor for unauthorized access attempts to backup file endpoints.

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
1704 Wgl FirmwareOperating system
Affected:= 2.0.6314

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 the device model
    Access the device's web interface or CLI and check the model number displayed in the device information or status page. Look for '1704-WGL' or 'BDCOM 1704' in the hardware model or device name.
    Affected if The device is not a BDCOM 1704-WGL model - if it is a different model, this CVE does not apply.
  2. Check the installed firmware version
    In the device's web interface, navigate to System Info, Device Status, or About page. Alternatively, use the CLI command 'show version' or 'system-info' to retrieve the firmware version number.
    Affected if The firmware version is exactly 2.0.6314 - only this specific version is listed as affected in the CVE.
  3. Verify backup file endpoint accessibility
    Attempt to access the URL path '/param.file.tgz' on the device's IP address using a web browser or curl command: curl http://DEVICE_IP/param.file.tgz
    Affected if The backup file downloads without requiring authentication or login - this indicates the improper access control vulnerability is present.
  4. Confirm backup file contains sensitive data
    If the file downloads successfully, extract and inspect the .tgz file to verify it contains configuration data such as network settings, credentials, or other sensitive parameters.
    Affected if The downloaded backup file contains unencrypted network configuration or credential data - confirming the information disclosure impact.

If the device is a BDCOM 1704-WGL running firmware version 2.0.6314 AND the /param.file.tgz endpoint is accessible without authentication, the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the device's management interface, implement proper authentication for backup file downloads, and contact BDCOM for firmware patches. As a compensating control, monitor for unauthorized access attempts to backup file endpoints.

Fix this in 1704 Wgl Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0659 — 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-0659 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