CVE-2012-1475
First published: Wed Mar 14 2012(Updated: )
Unspecified vulnerability in the YagattaTalk Messenger (com.iskoot.yagatta.yagattatalk) application 1.00.01.08 for Android has unknown impact and attack vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Yagattatalk Messenger | =1.00.01.08 | |
| Android |
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-2012-1475?
The severity of CVE-2012-1475 is currently unspecified, as the exact impact and attack vectors are unknown.
How do I fix CVE-2012-1475?
To address CVE-2012-1475, it is recommended to update or uninstall the YagattaTalk Messenger application if possible.
What software is affected by CVE-2012-1475?
CVE-2012-1475 specifically affects YagattaTalk Messenger version 1.00.01.08 for Android.
Are there any known exploits for CVE-2012-1475?
As of now, there are no known exploits publicly reported for CVE-2012-1475.
Who is the vendor responsible for the software related to CVE-2012-1475?
The vendor responsible for YagattaTalk Messenger related to CVE-2012-1475 is Qualcomm.
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- agent/severity
- agent/references
- agent/author
- agent/description
- agent/event
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/qualcomm
- canonical/yagattatalk messenger
- version/yagattatalk messenger/1.00.01.08
- vendor/google
- canonical/android