# CVE-2024-28146: Hardcoded credentials

> Attackers can use hardcoded credentials to access database servers, decrypt firmware updates, and potentially execute code on Image Access Scan2Net devices.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-84p4-9xrj-9rj5

## What is CVE-2024-28146?

CVE-2024-28146 is a high-severity vulnerability in Image Access GmbH Scan2Net, published on 12 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The application uses several hard-coded credentials to encrypt config files during backup, to decrypt the new firmware during an update and some passwords allow a direct connection to the database server of the affected device.

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

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


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

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

## Is CVE-2024-28146 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28146 is a high-severity vulnerability in Image Access GmbH Scan2Net, published on 12 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28146 in the wild and no public exploit code.

Affected product: Image Access GmbH Scan2Net. 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-28146/ (Markdown: https://insights.sbomify.com/CVE-2024-28146/index.md)
```

## Sources

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

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