CVE-2025-62674
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 · uneditedThe affected product allows unauthenticated access to Real Time Streaming Protocol (RTSP) services, which may allow an attacker unauthorized access to camera configuration information.
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 · high confidenceThe vulnerability allows unauthenticated access to RTSP (Real Time Streaming Protocol) services on affected products, enabling attackers to retrieve camera configuration information without any credentials. RTSP is commonly used for controlling media streaming in surveillance cameras and video management systems.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
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 RTSP service exposureScan your network for open ports 554 (RTSP) and 8554 (alternate RTSP). Use 'netstat -an | grep -E "(554|8554)"' or a port scanner to determine if RTSP ports are listening on any interface.Affected if RTSP ports 554 or 8554 are open and listening on network interfaces accessible to untrusted parties
-
Verify RTSP authentication is requiredAttempt to connect to the RTSP endpoint without credentials using a tool like FFmpeg (ffmpeg -rtsp_transport tcp rtsp://<target>/stream) or a simple telnet/netcat to port 554. Check if the service accepts the connection without prompting for authentication.Affected if RTSP service accepts connections and returns stream data or configuration without requiring username/password
-
Check RTSP configuration settingsAccess the camera or VMS administrative interface and navigate to Network Settings or RTSP configuration. Look for options labeled 'Authentication', 'Enable Authentication', or similar. Verify that authentication is set to 'Enabled' or 'Required'.Affected if Authentication is explicitly disabled or set to 'None' for RTSP services
-
Review network access controlsExamine firewall rules, ACLs, or network segmentation that control access to RTSP ports. Check if the RTSP service is bound to 0.0.0.0 or an externally accessible interface rather than localhost/internal-only interfaces.Affected if RTSP is accessible from networks outside the trusted internal network or from any untrusted IP address
-
Determine installed product versionConsult the camera or VMS web interface (typically under System, About, or Status sections), or check the firmware/software version via SNMP, vendor tools, or documentation. Compare the version to any vendor-published affected version lists.Affected if The installed version matches or falls within vendor-specified affected version ranges
A user is affected if RTSP services are running, accessible from untrusted networks, and do not require authentication 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 dataEnable authentication on RTSP services and restrict network access to trusted IP addresses or networks. Review and apply vendor patches when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62674 — 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-62674 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