# CVE-2024-33753: Missing authorization in n/a

> Attackers can change administrator and user credentials without authorization, leading to full device takeover.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-m854-6wh4-fmg2

## What is CVE-2024-33753?

CVE-2024-33753 is a high-severity missing authorization vulnerability in n/a, published on 6 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Section Camera V2.5.5.3116-S50-SMA-B20160811 and earlier versions allow the accounts and passwords of administrators and users to be changed without authorization.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2024-33753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33753 is a high-severity missing authorization vulnerability in n/a, published on 6 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33753 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-2024-33753/ (Markdown: https://insights.sbomify.com/CVE-2024-33753/index.md)
```

## Sources

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

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