# CVE-2009-5154: Hardcoded credentials in n/a

> Attackers can gain administrative access to MOBOTIX S14 cameras using the default password 'meinsm'.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j6w3-479p-g3p9

## What is CVE-2009-5154?

CVE-2009-5154 is a critical vulnerability in n/a, published on 9 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on MOBOTIX S14 MX-V4.2.1.61 devices. There is a default password of meinsm for the admin account.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2009-5154?

It affects 1 product.


Products: Mobotix S14 Firmware.

## How do I fix CVE-2009-5154?

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

## Is CVE-2009-5154 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7674](https://insights.sbomify.com/CVE-2019-7674/): Weak cryptography in n/a (critical 9.8)
- [CVE-2019-12502](https://insights.sbomify.com/CVE-2019-12502/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-7673](https://insights.sbomify.com/CVE-2019-7673/): Weak cryptography in n/a (high 7.5)
- [CVE-2019-7675](https://insights.sbomify.com/CVE-2019-7675/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5154 and fix it if it is affected.

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

## Sources

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

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