Ingenico Telium 2 9.32.03 TRACE Protocol Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Ingenico Telium 2 9.32.03. It has been classified as critical. Affected is an unknown function of the component TRACE Protocol Handler. Performing a manipulation results in Local Privilege Escalation. This vulnerability is identified as CVE-2018-17768. The attack may be carried out on the physical device. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Ingenico Telium 2 9.32.03. It has been classified as critical. This affects an unknown code block of the component TRACE Protocol Handler. The manipulation with an unknown input leads to a local privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Ingenico Telium 2 POS terminals have an insecure TRACE protocol. This is fixed in Telium 2 SDK v9.32.03 patch N.
The weakness was released 09/09/2020. This vulnerability is uniquely identified as CVE-2018-17768 since 09/28/2018. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Applying the patch 9.32.03 Patch N is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-161065, VDB-161064, VDB-161063 and VDB-161060. 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: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.8
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.8
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: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 9.32.03 Patch N
Timeline
09/28/2018 🔍09/09/2020 🔍
09/10/2020 🔍
09/10/2020 🔍
Sources
Status: Not definedCVE: CVE-2018-17768 (🔍)
GCVE (CVE): GCVE-0-2018-17768
GCVE (VulDB): GCVE-100-161061
See also: 🔍
Entry
Created: 09/10/2020 06:53Updated: 09/10/2020 06:58
Changes: 09/10/2020 06:53 (37), 09/10/2020 06:58 (16)
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.