CVE-2025-9983
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGALAYOU 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGALAYOU G2 cameras stream video via RTSP protocol with randomly generated default credentials that are supposed to protect access. However, these credentials are not actually enforced by the firmware - the RTSP stream can be accessed without any authentication. This is an authentication bypass allowing unauthenticated remote viewing of video feeds.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GALAYOU G2 camera on networkCheck your device inventory or network scan for GALAYOU G2 camera models. You can also access the camera's web interface and look for the model number in the device info or settings page.Affected if You have a GALAYOU G2 camera deployed on your network.
-
Confirm RTSP is enabledAccess the camera's web interface and navigate to the network settings or stream settings page. Look for RTSP configuration options and verify whether RTSP streaming is turned on.Affected if RTSP streaming is enabled on the camera.
-
Locate RTSP URL and portIn the camera's RTSP settings, note the RTSP URL (typically rtsp://[camera-ip]:[port]/) and the port number (commonly 554 or 8554). This URL is needed for the next step.Affected if You have identified the RTSP endpoint URL for your camera.
-
Test RTSP access without authenticationUsing an RTSP client (such as VLC media player, ffmpeg, or rtsp-client tools), attempt to connect to the RTSP URL without providing any username or password. For example: rtsp://[camera-ip]:[port]/ or use ffplay rtsp://[camera-ip]:[port]/.Affected if The RTSP stream plays or connects successfully without providing any credentials, indicating authentication is not enforced.
You are affected if you have a GALAYOU G2 camera with RTSP enabled and can access the video stream without entering any credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond and no patch is available, implement compensating controls: isolate camera networks via VLAN segmentation, restrict RTSP port access with firewall rules to only authorized management IPs/subnets, and consider replacing with cameras that properly enforce RTSP authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9983 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9983 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data