# CVE-2025-9983: Lack of Authentication for RTSP stream

> Attackers can access RTSP video streams without authentication because the camera ignores configured credentials, exposing live video feeds.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 22 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-7838-283v-mwh7

## What is CVE-2025-9983?

CVE-2025-9983 is a high-severity missing authorization vulnerability in GALAYOU G2, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GALAYOU G2 cameras stream video output via RTSP streams. By default these streams are protected by randomly generated credentials. However these credentials are not required to access the stream. Changing these values does not change camera's behavior.

The vendor did not respond in any way. Only version 11.100001.01.28 was tested, other versions might also be vulnerable.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-9983?


## How do I fix CVE-2025-9983?

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

## Is CVE-2025-9983 being exploited?

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

Public exploit code:

- CVE-2025-9983 POC Exploit (github_poc): https://github.com/sohaibeb/CVE-2025-9983

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9983 and fix it if it is affected.

What it is: CVE-2025-9983 is a high-severity missing authorization vulnerability in GALAYOU G2, published on 22 Sep 2025. 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-2025-9983 in the wild and no public exploit code.

Affected product: GALAYOU G2. 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-2025-9983/ (Markdown: https://insights.sbomify.com/CVE-2025-9983/index.md)
```

## Sources

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

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