# CVE-2023-0659: BDCOM 1704-WGL Backup File param.file.tgz information disclosure

> Remote attackers can access sensitive information via the backup file handler in BDCOM 1704-WGL devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-xgqm-fh99-4q88

## What is CVE-2023-0659?

CVE-2023-0659 is a medium-severity vulnerability in BDCOM 1704-WGL, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-0659?

It affects 1 product.


Products: Bdcom 1704-Wgl Firmware.

## How do I fix CVE-2023-0659?

No fix has been published for CVE-2023-0659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-0659 being exploited?

There is no known exploitation of CVE-2023-0659 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0659 and fix it if it is affected.

What it is: CVE-2023-0659 is a medium-severity vulnerability in BDCOM 1704-WGL, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0659 in the wild and no public exploit code.

Affected product: BDCOM 1704-WGL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-0659/ (Markdown: https://insights.sbomify.com/CVE-2023-0659/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-0659
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-0659
- OSV: https://osv.dev/vulnerability/CVE-2023-0659

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-0659/
Summaries are generated and may contain mistakes; the official description above is the record.