# CVE-2008-5848: Hardcoded credentials in n/a

> Remote attackers can access the Advantech ADAM-6000 module using the default password to monitor or control Modbus/TCP I/O activity.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wp78-3mjg-28r3

## What is CVE-2008-5848?

CVE-2008-5848 is a critical vulnerability in n/a, published on 6 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Advantech ADAM-6000 module has 00000000 as its default password, which makes it easier for remote attackers to obtain access through an HTTP session, and (1) monitor or (2) control the module's Modbus/TCP I/O activity.

Weakness: CWE-255

## Which versions are affected by CVE-2008-5848?

It affects 14 products.


Products: Advantech Adam-6015, Advantech Adam-6017, Advantech Adam-6018, Advantech Adam-6022, Advantech Adam-6024, Advantech Adam-6050, Advantech Adam-6050w, Advantech Adam-6051, Advantech Adam-6051w, Advantech Adam-6052, Advantech Adam-6060, Advantech Adam-6060w, Advantech Adam-6066, Advantech Adam-6501.

## How do I fix CVE-2008-5848?

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

## Is CVE-2008-5848 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5848 and fix it if it is affected.

What it is: CVE-2008-5848 is a critical vulnerability in n/a, published on 6 Jan 2009. 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-2008-5848 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-2008-5848/ (Markdown: https://insights.sbomify.com/CVE-2008-5848/index.md)
```

## Sources

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

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