| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Grocy 4.0.3. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component QR Code Handler. Executing a manipulation can lead to information disclosure. This vulnerability appears as CVE-2023-48199. The attack requires local access. There is no available exploit.
Details
A vulnerability was found in Grocy 4.0.3. It has been declared as problematic. This vulnerability affects some unknown processing of the component QR Code Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
An issue in Grocy v.4.0.3 allows a local attacker to execute arbitrary code and obtain sensitive information via the QR code funciton in the manageapikeys component.
The weakness was presented 11/16/2023. After contacting the project maintainer of Grocy for a coordinated disclosure of CVE-2024-8370 he requested via email on 2024-09-01 and 2024-09-02 the removal of all mentions of the product from VulDB. We do never comply with such suppression requests as explained in our Revoke Policy which is why the vulnerability entries remain available to their full extent. This vulnerability was named CVE-2023-48199 since 11/13/2023. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-52279). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.3
VulDB Temp Score: 3.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: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/13/2023 🔍11/16/2023 🔍
11/16/2023 🔍
02/26/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-48199 (🔍)
GCVE (CVE): GCVE-0-2023-48199
GCVE (VulDB): GCVE-100-245608
EUVD: 🔍
Entry
Created: 11/16/2023 07:46Updated: 02/26/2026 18:39
Changes: 11/16/2023 07:46 (36), 12/12/2023 15:00 (1), 12/12/2023 15:03 (11), 09/16/2024 07:01 (16), 09/29/2025 18:58 (1), 02/26/2026 18:39 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.