dbcve.org
My Ngemc AccountApplication · Ngemc

CVE-2014-7449

MEDIUM · 5.4 CVSS v2.0 Published 2014-10-19
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 My NGEMC Account (aka com.ngemc.smartapps) application 1.153.0034 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 My NGEMC Account Android application version 1.153.0034 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept traffic and obtain sensitive information by presenting forged certificates.

MitigationImplement proper SSL certificate validation using certificate pinning or a properly configured TrustManager to ensure the app only accepts certificates from trusted Certificate Authorities.

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
My Ngemc AccountApplication
Affected:= 1.153.0034

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. Identify if My NGEMC Account app is installed
    On the Android device, go to Settings > Apps and search for 'My NGEMC Account' or 'Ngemc', or use ADB command: adb shell pm list packages | grep -i ngemc
    Affected if The application package com.ngemc.myaccount or similar is found on the device
  2. Determine the installed version number
    In Android Settings > Apps > My NGEMC Account > Version information, or use ADB: adb shell dumpsys package <package_name> | grep versionName
    Affected if The displayed version is 1.153.0034
  3. Confirm the SSL certificate validation is not implemented
    Review the application APK or conduct network traffic analysis using a proxy with a self-signed certificate to observe if the app accepts the invalid certificate without warning
    Affected if The app accepts an invalid or self-signed certificate during MITM testing, confirming the lack of X.509 validation

If My NGEMC Account version 1.153.0034 is installed and accepts invalid SSL certificates, the environment is affected by CVE-2014-7449.

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

Implement proper SSL certificate validation using certificate pinning or a properly configured TrustManager to ensure the app only accepts certificates from trusted Certificate Authorities.

Fix this in My Ngemc Account Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7449 — 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-7449 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