| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in linqi up to 1.4.0.0 on Windows. It has been classified as problematic. This issue affects some unknown processing. Performing a manipulation results in hard-coded password. This vulnerability was named CVE-2024-33867. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in linqi up to 1.4.0.0 on Windows. This affects an unknown code block. The manipulation with an unknown input leads to a hard-coded password vulnerability. CWE is classifying the issue as CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. This is going to have an impact on confidentiality. The summary by CVE is:
An issue was discovered in linqi before 1.4.0.1 on Windows. There is a hardcoded password salt.
The advisory is shared at linqi.help. This vulnerability is uniquely identified as CVE-2024-33867 since 04/27/2024. The exploitability is told to be difficult. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1078.001 for this issue.
Upgrading to version 1.4.0.1 eliminates this vulnerability. The upgrade is hosted for download at linqi.help.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.6
VulDB Temp Score: 2.5
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: Hard-coded passwordCWE: CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: linqi 1.4.0.1
Timeline
04/27/2024 🔍05/14/2024 🔍
05/14/2024 🔍
04/28/2025 🔍
Sources
Advisory: linqi.helpStatus: Confirmed
CVE: CVE-2024-33867 (🔍)
GCVE (CVE): GCVE-0-2024-33867
GCVE (VulDB): GCVE-100-264213
Entry
Created: 05/14/2024 17:14Updated: 04/28/2025 20:45
Changes: 05/14/2024 17:14 (52), 04/28/2025 20:45 (3)
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.