# CVE-2021-34544: Information disclosure in n/a

> Cleartext passwords stored in HTML files allow attackers with device access to read sensitive credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Dec 2021
- **Updated:** 11 Nov 2024
- **Also known as:** GHSA-wrh5-96rf-7qq2

## What is CVE-2021-34544?

CVE-2021-34544 is a medium-severity vulnerability in n/a, published on 7 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Solar-Log 500 before 2.8.2 Build 52 23.04.2013. In /export.html, email.html, and sms.html, cleartext passwords are stored. This may allow sensitive information to be read by someone with access to the device. Fixed with 3.0.0-60 11.10.2013 for SL 200, 500, 1000 / not existing for SL 250, 300, 1200, 2000, SL 50 Gateway, SL Base.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2021-34544?

It affects 1 product.


Products: Bkw Solar-Log 500 Firmware.

## How do I fix CVE-2021-34544?

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

## Is CVE-2021-34544 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-34543](https://insights.sbomify.com/CVE-2021-34543/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34544 and fix it if it is affected.

What it is: CVE-2021-34544 is a medium-severity vulnerability in n/a, published on 7 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-34544 in the wild and no public exploit code.

Affected product: n/a. 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-2021-34544/ (Markdown: https://insights.sbomify.com/CVE-2021-34544/index.md)
```

## Sources

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

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