Instagram 4.0.2/4.1.2 on Android Signature Key missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Instagram 4.0.2/4.1.2 on Android. The affected element is an unknown function of the component Signature Key Handler. This manipulation causes missing encryption. In addition, an exploit is available.
Details
A vulnerability has been found in Instagram 4.0.2/4.1.2 on Android (Social Network Software) and classified as critical. Affected by this vulnerability is some unknown processing of the component Signature Key Handler. The manipulation with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 07/21/2013. The weakness was presented 08/28/2013 by Georg Lukas with rt-solutions.de GmbH as Two Instagram Android App Security Vulnerabilities as not defined mailinglist post (Bugtraq). The advisory is shared at seclists.org. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 38 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at OSVDB (96696†). See VDB-10094 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
07/21/2013 🔍08/28/2013 🔍
08/28/2013 🔍
09/03/2013 🔍
03/21/2019 🔍
Sources
Advisory: Two Instagram Android App Security VulnerabilitiesResearcher: Georg Lukas
Organization: rt-solutions.de GmbH
Status: Not defined
GCVE (VulDB): GCVE-100-10093
OSVDB: 96696
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 09/03/2013 12:55Updated: 03/21/2019 15:33
Changes: 09/03/2013 12:55 (47), 03/21/2019 15:33 (2)
Complete: 🔍
Committer: olku
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.