paijp lte-pic32-writer 0.0.1 file information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in paijp lte-pic32-writer 0.0.1. This affects an unknown function. The manipulation results in file information disclosure. This vulnerability was named CVE-2023-46723. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as problematic has been found in paijp lte-pic32-writer 0.0.1. Affected is an unknown functionality. The manipulation with an unknown input leads to a file information disclosure vulnerability. CWE is classifying the issue as CWE-538. The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. This is going to have an impact on confidentiality. CVE summarizes:
lte-pic32-writer is a writer for PIC32 devices. In versions 0.0.1 and prior, those who use `sendto.txt` are vulnerable to attackers who known the IMEI reading the sendto.txt. The sendto.txt file can contain the SNS(such as slack and zulip) URL and API key. As of time of publication, a patch is not yet available. As workarounds, avoid using `sendto.txt` or use `.htaccess` to block access to `sendto.txt`.
The weakness was presented 10/31/2023 as GHSA-9qgg-ph2v-v4mh. The advisory is available at github.com. This vulnerability is traded as CVE-2023-46723 since 10/25/2023. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1083 by the MITRE ATT&CK project.
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 best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 8.9
CNA Vector (GitHub, Inc.): 🔍
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: File information disclosureCWE: CWE-538 / CWE-200 / CWE-284
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/25/2023 🔍10/31/2023 🔍
10/31/2023 🔍
11/24/2023 🔍
Sources
Product: github.comAdvisory: GHSA-9qgg-ph2v-v4mh
Status: Confirmed
CVE: CVE-2023-46723 (🔍)
GCVE (CVE): GCVE-0-2023-46723
GCVE (VulDB): GCVE-100-244098
Entry
Created: 10/31/2023 18:09Updated: 11/24/2023 18:02
Changes: 10/31/2023 18:09 (48), 11/24/2023 18:02 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.