CVE-2014-5846
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 · uneditedThe Fairy Princess Makeover Salon (aka com.mobgams.dressup.fairy.princess.makeover) application 1.7 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 confidenceThe Fairy Princess Makeover Salon Android application version 1.7 fails to validate X.509 certificates from SSL servers, enabling man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates and steal sensitive data.
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= 1.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Fairy Princess Makeover Salon is installedOn the Android device, go to Settings > Apps > All Apps and search for 'Fairy Princess Makeover Salon' or 'Mobgams', or use the command 'adb shell pm list packages' to list all installed packages and grep for 'mobgams' or 'fairy'Affected if The app is present on the device
-
Determine the installed app versionIn Settings > Apps > All Apps > Fairy Princess Makeover Salon, note the version number displayed under the app name, or use 'adb shell dumpsys package com.mobgams.fairyprincesssalon' to retrieve version infoAffected if The version shown is 1.7
-
Verify the app connects to network serversUse network monitoring tools such as 'adb shell netstat' or a network sniffer on a separate machine to observe if the app makes outbound HTTPS connections when in useAffected if The app transmits data over network without proper certificate validation
-
Inspect app SSL/TLS implementation (requires APK)Obtain the APK file (via 'adb backup' or APK extraction from device), decompile using tools like jadx or apktool, and examine source code for HttpURLConnection, HttpsURLConnection, or Apache HTTP Client usage to verify if certificate validation is properly implemented (look for custom TrustManager implementations or lack thereof)Affected if The code shows no certificate chain validation or uses an untrusted custom TrustManager allowing all certificates
A user is affected if the Fairy Princess Makeover Salon app version 1.7 is installed and transmits sensitive data over network connections without proper SSL certificate validation.
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 dataImplement proper SSL/TLS certificate validation in the Android app, preferably through certificate pinning or proper X.509 certificate chain verification to ensure the app only trusts legitimate server certificates.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5846 — 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-2014-5846 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