CVE-2024-52052
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 · uneditedWowza Streaming Engine below 4.9.1 permits an authenticated Streaming Engine Manager administrator to define a custom application property and poison a stream target for high-privilege remote code execution.
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 confidenceWowza Streaming Engine versions before 4.9.1 contain an authenticated RCE vulnerability where a Streaming Engine Manager administrator can define custom application properties that poison stream targets, leading to high-privilege remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.3.0, < 4.9.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Wowza Streaming Engine versionCheck the version file or startup logs in the Wowza installation directory. Common locations include version.txt in the root folder or the About page in Streaming Engine Manager.Affected if The installed version is 4.3.0 through 4.9.0 (any version >= 4.3.0 but < 4.9.1)
-
Confirm Streaming Engine Manager is accessibleVerify that the Manager web interface is running and accessible on the configured admin port (typically 8088 or 8090). Check if the Manager service is active.Affected if Manager is accessible, as this is required for an administrator to define the malicious custom application properties
-
Locate application configuration filesNavigate to the application configuration directory in the Wowza content folder. Custom application properties are typically stored in Application.xml or similar XML configuration files under the conf/[application-name]/ directory.Affected if Custom application properties are defined in the application configuration that could poison stream targets
-
Review custom stream target configurationsInspect the Stream Targets configuration within each application for any custom properties or scripts that appear suspicious, especially those that could enable remote code execution.Affected if Custom stream target properties contain unsanitized or potentially malicious definitions that could lead to RCE
Your environment is affected if you run Wowza Streaming Engine version 4.3.0 through 4.9.0 and have Streaming Engine Manager accessible with custom application or stream target configurations present.
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.
dbcve · scoped4.9.1
Upgrade to Wowza Streaming Engine 4.9.1 or later. If immediate patching is not possible, restrict admin access to trusted personnel and monitor for suspicious custom application property definitions.
4.9.1 or later
- Download Wowza Streaming Engine 4.9.1 or later from the official Wowza website (www.wowza.com)
- Stop the Wowza Streaming Engine service
- Install the 4.9.1 or later version following Wowza's standard upgrade procedure
- Restart the Wowza Streaming Engine service
- Verify the upgrade was successful by checking the version in the Streaming Engine Manager under System > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52052 — 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-52052 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