dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-33250

HIGH · 7.2 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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 Open-Source Technology Committee SRS real-time video server RS/4.0.268(Leo) and SRS/4.0.195(Leo) allows a remote attacker to execute arbitrary code via a crafted request.

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 remote code execution vulnerability exists in the SRS (Simple Realtime Server) video server versions 4.0.268(Leo) and 4.0.195(Leo). Attackers can exploit this by sending specially crafted requests to the server, allowing arbitrary code execution on the affected system.

MitigationUpgrade to a patched version of SRS or apply vendor-provided security updates. If immediate patching is not feasible, restrict network access to the SRS management interface and implement network segmentation to limit exposure.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 checks

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

  1. Identify SRS version
    Run the SRS binary with version flag (commonly 'srs -v' or './objs/srs -v' from the SRS installation directory) or check the server banner/response if exposed via API
    Affected if The version matches exactly 4.0.268(Leo) or 4.0.195(Leo)
  2. Confirm exact version number
    Compare the installed version string against the affected releases. SRS versions follow a 'major.minor.patch(build)' format (e.g., 4.0.268)
    Affected if The installed version is 4.0.268 or 4.0.195 exactly
  3. Check network exposure of SRS management interface
    Inspect network listeners and firewall rules to determine if the SRS API or management port (default 1985 for API, 8080 for HTTP) is accessible from untrusted networks
    Affected if The SRS management or API interface is exposed to the internet or untrusted internal hosts
  4. Review SRS configuration for exposed endpoints
    Examine the SRS configuration file (commonly srs.conf in /etc or the conf/ directory) for API or HTTP server settings that may handle specially crafted requests
    Affected if HTTP API or RTMP/HTTP callbacks are enabled and reachable

You are affected if your installed SRS version is exactly 4.0.268(Leo) or 4.0.195(Leo) AND the server management interface or API is network-accessible to attackers.

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

Upgrade to a patched version of SRS or apply vendor-provided security updates. If immediate patching is not feasible, restrict network access to the SRS management interface and implement network segmentation to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33250 — 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-2024-33250 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