goTenna Pro ATAK Plugin up to 1.9.12 Broadcast Key Name insertion of sensitive information into sent data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in goTenna Pro ATAK Plugin up to 1.9.12. Impacted is an unknown function of the component Broadcast Key Name Handler. Performing a manipulation results in insertion of sensitive information into sent data. This vulnerability was named CVE-2024-41931. The attack needs to be approached within the local network. There is no available exploit.
Details
A vulnerability classified as problematic has been found in goTenna Pro ATAK Plugin up to 1.9.12. This affects some unknown processing of the component Broadcast Key Name Handler. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. CWE is classifying the issue as CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. This is going to have an impact on confidentiality. The summary by CVE is:
The goTenna Pro ATAK Plugin broadcast key name is always sent unencrypted and could reveal the location of operation.
The weakness was presented by Erwin Karincic, Clayton Smith and Dale Wooden as icsa-24-270-05. The advisory is shared at cisa.gov. This vulnerability is uniquely identified as CVE-2024-41931 since 09/24/2024. The exploitability is told to be difficult. Access to the local network is required for this attack to succeed. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 3.9VulDB Meta Temp Score: 3.9
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 4.3
CNA Vector (icscert): 🔍
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: Insertion of sensitive information into sent dataCWE: CWE-201 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: 🔍
Timeline
09/24/2024 🔍09/26/2024 🔍
09/26/2024 🔍
10/07/2024 🔍
Sources
Advisory: icsa-24-270-05Researcher: Erwin Karincic, Clayton Smith, Dale Wooden
Status: Not defined
CVE: CVE-2024-41931 (🔍)
GCVE (CVE): GCVE-0-2024-41931
GCVE (VulDB): GCVE-100-278613
Entry
Created: 09/26/2024 21:09Updated: 10/07/2024 21:18
Changes: 09/26/2024 21:09 (75), 10/01/2024 01:49 (1), 10/07/2024 21:18 (11)
Complete: 🔍
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.