# CVE-2024-47295: Hardcoded credentials in Web Config

> Remote attackers can exploit insecure initial password settings to gain administrative control over Epson Web Config devices.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 1 Oct 2024
- **Updated:** 11 Nov 2024
- **Also known as:** GHSA-x2wv-q3cc-vc36

## What is CVE-2024-47295?

CVE-2024-47295 is a high-severity vulnerability in SEIKO EPSON CORPORATION Web Config, published on 1 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insecure initial password configuration issue in SEIKO EPSON Web Config allows a remote unauthenticated attacker to set an arbitrary password and operate the device with an administrative privilege. As for the details of the affected versions, see the information provided by the vendor under [References].

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2024-47295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47295 is a high-severity vulnerability in SEIKO EPSON CORPORATION Web Config, published on 1 Oct 2024. 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-2024-47295 in the wild and no public exploit code.

Affected product: SEIKO EPSON CORPORATION Web Config. 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-47295/ (Markdown: https://insights.sbomify.com/CVE-2024-47295/index.md)
```

## Sources

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

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