Intel Puma 5/6/7 on Asus CM-32 Packet denial of service

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Intel Puma 5/6/7 on Asus CM-32. This issue affects some unknown processing. The manipulation as part of Packet leads to denial of service. This vulnerability is listed as CVE-2017-15065. The attack may be initiated remotely. There is no available exploit. It is recommended to apply restrictive firewalling.
Details
A vulnerability was found in Intel Puma 5/6/7 on Asus CM-32 and classified as problematic. This issue affects an unknown code. The manipulation as part of a Packet leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
The Intel Puma 5, 6, and 7 chips, as used on ASUS CM-32 devices, allow remote attackers to cause a denial of service (performance degradation) by sending a moderate volume of small packets to many TCP or UDP ports. NOTE: Intel has advised that they are only a hardware manufacturer in this instance; they do NOT own the mitigation distribution channel for these chips. Any details about mitigations would need to come from ASUS.
The bug was discovered 11/29/2016. The weakness was presented 10/06/2017 (Website). The advisory is shared at badmodems.com. The identification of this vulnerability is CVE-2017-15065 since 10/06/2017. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 311 days. During that time the estimated underground price was around $5k-$25k.
Addressing this vulnerability is possible by firewalling .
See VDB-107572, VDB-107574, VDB-107575 and VDB-107576 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.intel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.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
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
11/29/2016 🔍10/06/2017 🔍
10/06/2017 🔍
10/07/2017 🔍
11/22/2019 🔍
Sources
Vendor: intel.comAdvisory: badmodems.com
Status: Not defined
CVE: CVE-2017-15065 (🔍)
GCVE (CVE): GCVE-0-2017-15065
GCVE (VulDB): GCVE-100-107573
See also: 🔍
Entry
Created: 10/07/2017 12:20Updated: 11/22/2019 17:57
Changes: 10/07/2017 12:20 (42), 11/22/2019 17:57 (2)
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.