# CVE-2023-34724: Privilege escalation in n/a

> Physical attackers can gain escalated privileges on the TECHView LA5570 Wireless Gateway via the UART interface.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** 28 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-x587-39r8-hwxf

## What is CVE-2023-34724?

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

### Official description

An issue was discovered in TECHView LA5570 Wireless Gateway 1.0.19_T53, allows physical attackers to gain escalated privileges via the UART interface.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Jaycar La5570 Firmware.

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

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

## Is CVE-2023-34724 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34723](https://insights.sbomify.com/CVE-2023-34723/): Path traversal in n/a (high 7.5)
- [CVE-2023-34725](https://insights.sbomify.com/CVE-2023-34725/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-34724 is a medium-severity vulnerability in n/a, published on 28 Aug 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-34724 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-34724/ (Markdown: https://insights.sbomify.com/CVE-2023-34724/index.md)
```

## Sources

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

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