dbcve.org
Albasit Artes Y DanzaApplication · Albasit Artes Y Danza Project

CVE-2014-6990

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The Albasit artes y danza (aka com.adianteventures.adianteapps.albasit_artes_y_danza) application 1.2 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

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

The Android application 'Albasit artes y danza' version 1.2 fails to verify X.509 certificates from SSL servers during HTTPS connections. This missing certificate validation allows man-in-the-middle attackers to present fraudulent certificates and intercept or tamper with encrypted communications between the app and legitimate servers.

MitigationThe application must implement proper SSL/TLS certificate validation using Android's standard security APIs, such as configuring a TrustManager that validates the certificate chain and potentially implementing certificate pinning for added security.

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
Albasit Artes Y DanzaApplication
Affected:= 1.2

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
Adjacent
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:A/AC:M/Au:N/C:P/I:P/A:P

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. Verify the Albasit artes y danza app is installed and check its version
    On an Android device, go to Settings > Apps > Albasit artes y danza, or use adb: 'adb shell pm list packages | grep albasit' then 'adb shell dumpsys package <package_name> | grep versionName'
    Affected if The app is installed and the versionName or versionCode shows exactly 1.2
  2. Determine if the app makes HTTPS network connections
    Use a network traffic analysis tool (such as Wireshark, mitmproxy, or Android Studio's Network Profiler) to observe the app's network behavior, or review the app's manifest and code for HTTPS URLs and network permission requests
    Affected if The app makes outbound HTTPS connections to remote servers
  3. Test for missing SSL certificate validation using a MITM proxy
    Set up a proxy (such as mitmproxy or Burp Suite) with a self-signed or untrusted certificate, configure the device to trust that proxy, launch the app, and attempt to intercept traffic. If the app connects successfully without certificate validation errors, the vulnerability is present
    Affected if The app successfully establishes HTTPS connections through an untrusted MITM proxy without any certificate validation errors or connection failures
  4. Static code analysis of SSL/TLS implementation
    Decompile the APK using tools like jadx or apktool, then inspect the source code for HttpsURLConnection, SSLContext, or TrustManager usage. Look for custom TrustManager implementations that bypass validation or missing hostname verification
    Affected if The code shows no proper TrustManager implementation, or contains implementations that accept all certificates (such as empty TrustManager or custom verifiers that always return true)

If the Albasit artes y danza app version 1.2 is installed and the app makes HTTPS connections without proper certificate chain validation (evidenced by accepting invalid certificates in testing or missing validation code), the environment is affected by CVE-2014-6990.

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

The application must implement proper SSL/TLS certificate validation using Android's standard security APIs, such as configuring a TrustManager that validates the certificate chain and potentially implementing certificate pinning for added security.

Fix this in Albasit Artes Y Danza Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-6990 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