| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Johnson & Johnson Animas OneTouch Ping. This issue affects some unknown processing. This manipulation causes cryptographic issue. This vulnerability is tracked as CVE-2016-5084. The attack is possible to be carried out remotely. No exploit exists. Further encryption should be added.
Details
A vulnerability was found in Johnson & Johnson Animas OneTouch Ping (affected version not known). It has been declared as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a cryptographic issue vulnerability. The CWE definition for the vulnerability is CWE-310. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Johnson & Johnson Animas OneTouch Ping devices do not use encryption for certain data, which might allow remote attackers to obtain sensitive information by sniffing the network.
The weakness was disclosed 10/05/2016 (Website). The advisory is shared at kb.cert.org. This vulnerability is known as CVE-2016-5084. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
It is possible to mitigate the problem by adding IPsec/SSH/SSL as an encryption mechanism.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93351†). The entries VDB-92438, VDB-92439 and VDB-92440 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cryptographic issueCWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: EncryptionStatus: 🔍
0-Day Time: 🔍
Encryption: IPsec/SSH/SSL
Timeline
05/26/2016 🔍10/05/2016 🔍
10/05/2016 🔍
10/06/2016 🔍
11/03/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Not defined
CVE: CVE-2016-5084 (🔍)
GCVE (CVE): GCVE-0-2016-5084
GCVE (VulDB): GCVE-100-92437
CERT: 🔍
SecurityFocus: 93351
See also: 🔍
Entry
Created: 10/06/2016 09:32Updated: 11/03/2024 13:01
Changes: 10/06/2016 09:32 (38), 01/27/2018 12:39 (10), 09/22/2022 12:51 (2), 09/22/2022 12:58 (11), 11/03/2024 13:01 (15)
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.