# CVE-2023-41010: Hardcoded credentials in n/a

> A local attacker can obtain sensitive information from the Tianyi Home Gateway by exploiting insecure permissions related to the default password parameter.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-53hj-p8fx-fw8x

## What is CVE-2023-41010?

CVE-2023-41010 is a medium-severity vulnerability in n/a, published on 14 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure Permissions vulnerability in Sichuan Tianyi Kanghe Communication Co., Ltd China Telecom Tianyi Home Gateway v.TEWA-700G allows a local attacker to obtain sensitive information via the default password parameter.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2023-41010?

It affects 1 product.


Products: Tianyisc Tewa-700g Firmware.

## How do I fix CVE-2023-41010?

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

## Is CVE-2023-41010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41010 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41010 and fix it if it is affected.

What it is: CVE-2023-41010 is a medium-severity vulnerability in n/a, published on 14 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41010 exists.

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-2023-41010/ (Markdown: https://insights.sbomify.com/CVE-2023-41010/index.md)
```

## Sources

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

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