| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in AttacheCase up to 3.3.0.0. This impacts an unknown function. Such manipulation leads to code injection. This vulnerability is uniquely identified as CVE-2018-0675. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in AttacheCase up to 3.3.0.0. Affected by this issue is an unknown functionality. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is integrity. CVE summarizes:
AttacheCase ver.3.3.0.0 and earlier allows an arbitrary script execution via unspecified vectors.
The bug was discovered 08/31/2018. The weakness was disclosed 09/04/2018 (Website). The advisory is shared for download at jvn.jp. This vulnerability is handled as CVE-2018-0675 since 11/26/2017. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-123571, VDB-123719 and VDB-123720 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/26/2017 🔍08/31/2018 🔍
09/04/2018 🔍
09/04/2018 🔍
09/05/2018 🔍
03/20/2020 🔍
Sources
Advisory: jvn.jpStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-0675 (🔍)
GCVE (CVE): GCVE-0-2018-0675
GCVE (VulDB): GCVE-100-123572
See also: 🔍
Entry
Created: 09/05/2018 06:52Updated: 03/20/2020 15:33
Changes: 09/05/2018 06:52 (56), 03/20/2020 15:33 (1)
Complete: 🔍
Cache ID: 216:5B3:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.