CVE-2024-51362
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 LSC Smart Connect Indoor IP Camera V7.6.32 is vulnerable to an information disclosure issue where live camera footage can be accessed through the RTSP protocol on port 8554 without requiring authentication. This allows unauthorized users with network access to view the camera's feed, potentially compromising user privacy and security. No credentials or special permissions are required, and access can be gained remotely over the network.
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 LSC Smart Connect Indoor IP Camera V7.6.32 exposes an unauthenticated RTSP service on port 8554, allowing any network-attacker to view live video footage without credentials or authentication.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the device modelAccess the camera's web interface or check network discovery for device identification (often shown as 'LSC Smart Connect' or similar)Affected if The device is an LSC Smart Connect Indoor IP Camera
-
Check the firmware versionLog into the camera's administrative interface and navigate to Settings > System > About, or use the manufacturer's discovery tool to retrieve the firmware versionAffected if The firmware version is exactly 7.6.32
-
Scan for open port 8554Use a network port scanner (such as 'nmap -p 8554 <camera_ip>' or 'netcat -nv <camera_ip> 8554') to test if RTSP port 8554 is listening and accessible from the networkAffected if Port 8554 is open and responds to connection attempts
-
Test RTSP authentication requirementAttempt to connect to the RTSP stream using a client (e.g., VLC media player with rtsp://<camera_ip>:8554/stream1) without providing any credentialsAffected if The stream plays without prompting for username or password
-
Verify RTSP authentication settingLog into the camera's admin interface and navigate to Network Settings > RTSP or Stream Settings to check if authentication is enabled or disabledAffected if RTSP authentication is disabled or set to 'none'
A user is affected if they have an LSC Smart Connect Indoor IP Camera on version 7.6.32 with port 8554 exposed and RTSP authentication disabled, allowing unauthenticated video access.
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 RTSP authentication in the camera's administrative interface, apply firmware updates if available, or restrict network access to port 8554 via firewall rules or network segmentation to prevent unauthorized viewing.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51362 — 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-2024-51362 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