# CVE-2024-37187: Advantech ADAM-5550 Weak Encoding for Password

> Attackers can easily decode user credentials transmitted by the Advantech ADAM-5550 due to weak Base64 encoding, leading to potential account takeover.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-8hrr-r493-96vh

## What is CVE-2024-37187?

CVE-2024-37187 is a medium-severity vulnerability in Advantech ADAM 5550, published on 27 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Advantech ADAM-5550 share user credentials with a low level of encryption, consisting of base 64 encoding.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-261 (Weak Encoding for Password)

## Which versions are affected by CVE-2024-37187?

It affects 1 product.


Products: Advantech Adam-5550 Firmware.

## How do I fix CVE-2024-37187?

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

## Is CVE-2024-37187 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37187 and fix it if it is affected.

What it is: CVE-2024-37187 is a medium-severity vulnerability in Advantech ADAM 5550, published on 27 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-37187 in the wild and no public exploit code.

Affected product: Advantech ADAM 5550. 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-2024-37187/ (Markdown: https://insights.sbomify.com/CVE-2024-37187/index.md)
```

## Sources

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

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