Air Sdk \& CompilerApplication · Adobe

CVE-2016-6936

HIGH · 7.5 CVSS v3.0 Published 2016-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Adobe AIR SDK & Compiler before 23.0.0.257 on Windows does not support Android runtime-analytics transport security, which might allow remote attackers to obtain sensitive information by leveraging access to a network over which analytics data is sent.

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 confidence

Adobe AIR SDK and Compiler versions before 23.0.0.257 fail to implement transport security (likely TLS/SSL) for analytics data transmitted from Android runtime applications. This allows network attackers on the same network path to intercept and read sensitive analytics information being sent from the mobile application.

MitigationUpgrade Adobe AIR SDK and Compiler to version 23.0.0.257 or later, which implements proper transport security for Android runtime analytics. Verify analytics functionality works correctly after the upgrade.

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
Air Sdk \& CompilerApplication
Affected:= 22.0.0.153

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Adobe AIR SDK installation
    Locate the Adobe AIR SDK/Compiler installation directory. Common paths include /opt/air or C:\Program Files\Adobe\Adobe AIR SDK on Linux/Windows. Look for the SDK folder and its version file or readme.
    Affected if Adobe AIR SDK version 22.0.0.153 or earlier is installed
  2. Check installed SDK version
    Open the SDK's readme.txt, version.xml, or run 'air -version' from the bin directory. Note the full version number displayed.
    Affected if Version number is 22.0.0.153 or any version earlier than 23.0.0.257
  3. Determine target Android application type
    Review the AIR application descriptor XML file (app.xml) for the target platform. Check if <android> element exists or if the application is being packaged for Android using -target android or -target apk.
    Affected if Building or packaging applications for Android platform using the AIR SDK
  4. Check for analytics feature usage
    Examine the ActionScript/AS3 source code for imports and usage of analytics modules such as 'analytics' or 'AdobeMobileLibrary'. Look for any analytics service configuration in the application code.
    Affected if Application code references or implements Adobe analytics or similar tracking functionality for Android
  5. Verify transport security implementation
    Review the application's network requests or analytics configuration to confirm if HTTPS/TLS is enforced for outbound data transmission. Check for any hardcoded HTTP URLs in analytics-related code.
    Affected if Analytics data is transmitted over unencrypted HTTP instead of HTTPS

You are affected if Adobe AIR SDK/Compiler version 22.0.0.153 or earlier is installed and you are building Android applications that transmit analytics data without encryption.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Adobe AIR SDK and Compiler to version 23.0.0.257 or later, which implements proper transport security for Android runtime analytics. Verify analytics functionality works correctly after the upgrade.

Fix this in Air Sdk \& Compiler Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6936 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-6936 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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