dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2023-50685

HIGH · 7.5 CVSS v3.1 Published 2024-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue in Hipcam Cameras RealServer v.1.0 allows a remote attacker to cause a denial of service via a crafted script to the client_port parameter.

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 confidence

A denial of service vulnerability exists in Hipcam Cameras RealServer v1.0 where a remote attacker can send a crafted script to the client_port parameter, causing the service to become unavailable.

MitigationRestrict network access to the RealServer through firewall rules or network segmentation. If no patch is available, consider replacing the affected device with a supported model.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Hipcam RealServer is installed
    Check running processes or installed software on the device for 'RealServer' or 'Hipcam' services
    Affected if The Hipcam RealServer service is present on the system
  2. Identify the RealServer version
    Query the service directly for its version information, or check application logs, configuration files, or the firmware image if accessible
    Affected if The installed version is v1.0 or falls within the affected range
  3. Verify network exposure of RealServer
    Check firewall rules, port listings, or network configuration to determine if the RealServer service (typically ports 8000-8002 or similar) is accessible from untrusted networks
    Affected if The RealServer service port is open to untrusted network segments or the internet
  4. Inspect service logs for exploitation attempts
    Review RealServer access logs and system logs for unusual requests to the client_port parameter or patterns indicating DoS activity
    Affected if Logs show repeated client_port parameter submissions or service degradation events
  5. Check service availability
    Attempt to connect to the RealServer or monitor its response time and availability
    Affected if The service is unresponsive, crashes frequently, or exhibits denial of service behavior

You are affected if Hipcam RealServer v1.0 is running and the service is network-accessible to remote attackers who can send requests to the client_port parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the RealServer through firewall rules or network segmentation. If no patch is available, consider replacing the affected device with a supported model.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50685 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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