# CVE-2024-47142: Hardcoded credentials in IXG-2C7

> Insufficiently protected credentials allow network-adjacent authenticated attackers to perform unintended operations on AIPHONE IXG systems.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-6245-p6w7-hf5m

## What is CVE-2024-47142?

CVE-2024-47142 is a medium-severity vulnerability in AIPHONE CO., LTD. IXG-2C7, published on 22 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AIPHONE IXG SYSTEM IXG-2C7 firmware Ver.2.03 and earlier and IXG-2C7-L firmware Ver.2.03 and earlier contain an issue with insufficiently protected credentials, which may allow a network-adjacent authenticated attacker to perform unintended operations.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2024-47142 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47142 is a medium-severity vulnerability in AIPHONE CO., LTD. IXG-2C7, published on 22 Nov 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-47142 in the wild and no public exploit code.

Affected product: AIPHONE CO., LTD. IXG-2C7. 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-47142/ (Markdown: https://insights.sbomify.com/CVE-2024-47142/index.md)
```

## Sources

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

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