# CVE-2022-46308: SGUDA U-Lock - Broken Access Control

> Remote attackers with general privileges can access, modify, and delete user information via privileged APIs due to incorrect authorization in SGUDA U-Lock.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2023
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-56rv-wmr6-9cpm

## What is CVE-2022-46308?

CVE-2022-46308 is a high-severity missing authorization vulnerability in SGUDA U-Lock, published on 2 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SGUDA U-Lock central lock control service’s user management function has incorrect authorization. A remote attacker with general user privilege can exploit this vulnerability to call privileged APIs to access, modify and delete user information.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-46308?

It affects 1 product.


Products: Sguda U-Lock Firmware.

## How do I fix CVE-2022-46308?

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

## Is CVE-2022-46308 being exploited?

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

## Other vulnerabilities in SGUDA U-Lock

- [CVE-2022-46307](https://insights.sbomify.com/CVE-2022-46307/): SGUDA U-Lock - Broken Access Control (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46308 and fix it if it is affected.

What it is: CVE-2022-46308 is a high-severity missing authorization vulnerability in SGUDA U-Lock, published on 2 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46308 in the wild and no public exploit code.

Affected product: SGUDA U-Lock. 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-2022-46308/ (Markdown: https://insights.sbomify.com/CVE-2022-46308/index.md)
```

## Sources

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

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