CVE-2019-19455
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 before 4.8.5 has Insecure Permissions which may allow a local attacker to escalate privileges in / usr / local / WowzaStreamingEngine / manager / bin / in the Linux version of the server by writing arbitrary commands in any file and execute them as root. This issue was resolved in Wowza Streaming Engine 4.8.5.
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 prior to 4.8.5 have insecure file permissions in the /usr/local/WowzaStreamingEngine/manager/bin/ directory on Linux installations. A local attacker with any level of access can write arbitrary commands to files in this directory and execute them with root privileges, achieving full local privilege escalation.
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.8.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Confirm Wowza Streaming Engine installationCheck if /usr/local/WowzaStreamingEngine/ directory exists on the system using 'ls -ld /usr/local/WowzaStreamingEngine/'Affected if The /usr/local/WowzaStreamingEngine directory exists on a Linux system
-
Determine installed versionLook for version information in the installation - check the startup scripts, version files, or run the engine and query its versionAffected if The installed version is earlier than 4.8.5 (e.g., 4.7.0, 4.8.0, 4.8.1, etc.)
-
Inspect permissions on manager/bin directoryRun 'ls -la /usr/local/WowzaStreamingEngine/manager/bin/' to view ownership and permissions on files in this directoryAffected if The directory or its contents are writable by non-root users (permission bits show 'w' for others or group, or ownership is not root)
-
Check if Wowza service runs as rootExamine the service startup configuration or process owner - check the init script or systemd service file to see what user the process runs asAffected if The Wowza service runs with root privileges
A system is affected if Wowza Streaming Engine version is prior to 4.8.5 AND the /usr/local/WowzaStreamingEngine/manager/bin/ directory is writable by non-root users AND the service runs as root, allowing local privilege escalation.
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.8.5
Upgrade to Wowza Streaming Engine 4.8.5 or later. Additionally, review and restrict file permissions on the manager/bin directory to follow least-privilege principles.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19455 — 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-2019-19455 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