treasonSMS 1.0.8 on iPhone Send Messages persistent cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in treasonSMS 1.0.8 on iPhone. Affected by this issue is some unknown functionality of the component Send Messages. Performing a manipulation results in cross site scripting (persistent). The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability classified as problematic has been found in treasonSMS 1.0.8 on iPhone. This affects an unknown functionality of the component Send Messages. The manipulation with an unknown input leads to a cross site scripting vulnerability (persistent). CWE is classifying the issue as CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. This is going to have an impact on integrity.
The weakness was presented 04/22/2012 by Benjamin Kunz Mejri as VL-ID 154 as not defined advisory (Website). It is possible to read the advisory at vulnerability-lab.com. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
A public exploit has been developed by Benjamin Kunz Mejri and been published immediately after the advisory. The exploit is shared for download at vulnerability-lab.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
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
Name: persistentClass: Cross site scripting / persistent
CWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Benjamin Kunz Mejri
Download: 🔍
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
04/22/2012 🔍04/22/2012 🔍
09/07/2016 🔍
04/11/2019 🔍
Sources
Advisory: VL-ID 154Researcher: Benjamin Kunz Mejri
Status: Not defined
GCVE (VulDB): GCVE-100-91323
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/07/2016 20:35Updated: 04/11/2019 16:49
Changes: 09/07/2016 20:35 (44), 04/11/2019 16:49 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.