CVE-2019-12936
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 · uneditedBlueStacks App Player 2, 3, and 4 before 4.90 allows DNS Rebinding for attacks on exposed IPC functions.
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 confidenceBlueStacks App Player versions 2, 3, and 4 before 4.90 contains exposed IPC (Inter-Process Communication) functions that can be accessed through DNS rebinding attacks. DNS rebinding allows attackers to bypass same-origin policy and access internal application functions by controlling DNS responses to point to localhost or internal network addresses.
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.90CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Confirm BlueStacks App Player is installedLook for BlueStacks processes running (e.g., BlueStacks.exe, BSTokenManager.exe, HD-LogCollector.exe) or check for BlueStacks installation directory in Program FilesAffected if BlueStacks processes or installation directory is found on the system
-
Identify the installed BlueStacks versionCheck the version information of the BlueStacks executable (typically BlueStacks.exe in the installation folder) by right-clicking and selecting Properties, or use command line tools to query version infoAffected if The version displayed is 2.x, 3.x, or 4.x with a build number lower than 4.90
-
Compare version against affected rangeThe affected version range is any BlueStacks App Player version below 4.90, which includes all versions 2.x, 3.x, and early 4.x releasesAffected if The installed version is less than 4.90 (for example, 4.70, 4.60, 3.x, or 2.x)
-
Verify the IPC interface is reachableThe vulnerability allows DNS rebinding attacks to access internal IPC functions - this is a built-in exposure in affected versions rather than a configurable featureAffected if BlueStacks is running and accessible on localhost or network interfaces with any version below 4.90
A system is affected if BlueStacks App Player version 2.x, 3.x, or any 4.x version below 4.90 is installed and running on the machine.
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.90
Upgrade BlueStacks App Player to version 4.90 or later. If upgrading is not possible, implement network-level protections such as DNS rebinding guards or restrict access to the application's IPC endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12936 — 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-12936 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