CVE-2018-7048
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 · uneditedAn issue was discovered in Wowza Streaming Engine before 4.7.1. There is a denial of service (memory consumption) via a crafted HTTP 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 · high confidenceWowza Streaming Engine before version 4.7.1 is vulnerable to a denial of service attack via crafted HTTP requests that cause excessive memory consumption. Remote attackers can trigger this vulnerability by sending specially crafted HTTP requests that lead to uncontrolled memory allocation, exhausting server resources.
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.7.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Wowza Streaming Engine is installedLocate the Wowza Streaming Engine installation directory and identify the product. Common installation paths include /usr/local/WowzaStreamingEngine or C:\Program Files\WowzaStreamingEngine on Windows.Affected if Wowza Streaming Engine software is present on the system
-
Determine the installed versionCheck the version of Wowza Streaming Engine. The version information is typically available in the software documentation, admin interface, or version manifest file within the installation directory.Affected if The installed version is any version prior to 4.7.1
-
Compare version against the affected rangeCompare your identified version number to 4.7.1. Any version lower than 4.7.1 falls within the affected range.Affected if The installed version is less than 4.7.1
-
Confirm HTTP interface exposureDetermine if the Wowza Streaming Engine HTTP interface is accessible from network locations. Check server firewall rules, network ACLs, and Wowza configuration for HTTP listener bindings.Affected if The HTTP interface is exposed to network access and the installed version is below 4.7.1
You are affected if Wowza Streaming Engine is installed with a version lower than 4.7.1 and its HTTP interface is network-accessible.
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 data4.7.1
Upgrade Wowza Streaming Engine to version 4.7.1 or later to obtain the patch for this vulnerability. Consider implementing rate limiting or request size restrictions on the HTTP interface as an additional hardening measure.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7048 — 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-2018-7048 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