CVE-2019-11351
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 · uneditedTeamSpeak 3 Client before 3.2.5 allows remote code execution in the Qt framework.
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 confidenceTeamSpeak 3 Client before version 3.2.5 contains a remote code execution vulnerability in its Qt framework component. The vulnerability allows an attacker to execute arbitrary code on the affected client system through the Qt framework.
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< 3.2.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 if TeamSpeak 3 Client is installedSearch for the TeamSpeak 3 executable (ts3client.exe on Windows, ts3client on Linux/Mac) in common installation directories or use system search utilities to locate the TeamSpeak client applicationAffected if TeamSpeak 3 Client is found on the system
-
Determine the installed TeamSpeak 3 Client versionRight-click the TeamSpeak executable and view its properties, or run the client with a version flag if available (such as --version), or check within the client interface under Help > AboutAffected if The version displayed is lower than 3.2.5
-
Verify the Qt framework component is presentCheck the TeamSpeak installation directory for Qt-related DLLs or libraries (commonly named qt*.dll on Windows or libQt*.so on Linux) which indicate the bundled Qt framework componentAffected if Qt framework libraries are present in the TeamSpeak installation directory and the client version is below 3.2.5
-
Confirm vulnerability applicabilityCross-reference the exact version number found with the affected range: any version before 3.2.5 contains the vulnerable Qt framework componentAffected if The installed TeamSpeak 3 Client version is any release prior to 3.2.5
A user is affected if TeamSpeak 3 Client version 3.2.5 or later is not installed, as versions below this contain the vulnerable Qt framework component that allows remote code execution.
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 data3.2.5
Upgrade TeamSpeak 3 Client to version 3.2.5 or later to remediate this vulnerability.
- 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-11351 — 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-11351 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