CVE-2014-6733
First published: Fri Sep 26 2014(Updated: )
The My T-Mobile (aka at.tmobile.android.myt) application @7F0C0030 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.
Credit: cret@cert.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| T-Mobile My T-Mobile | =\@7f0c0030 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2014-6733?
CVE-2014-6733 has a high severity rating due to its potential for man-in-the-middle attacks.
How can I fix CVE-2014-6733?
To fix CVE-2014-6733, ensure you update the My T-Mobile application to the latest version that includes proper SSL certificate validation.
What type of attacks does CVE-2014-6733 enable?
CVE-2014-6733 enables man-in-the-middle attacks, allowing attackers to spoof SSL servers and intercept sensitive information.
Which application is affected by CVE-2014-6733?
CVE-2014-6733 affects the My T-Mobile application version @7F0C0030 for Android.
What are the implications of not addressing CVE-2014-6733?
Not addressing CVE-2014-6733 can lead to the exposure of sensitive user information to attackers.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/references
- agent/author
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/t-mobile
- canonical/t-mobile my t-mobile
- version/t-mobile my t-mobile/\@7f0c0030