Signum FARA up to 5.0.80.34 SQLite Database hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Signum FARA up to 5.0.80.34 and classified as critical. This issue affects some unknown processing of the component SQLite Database. Such manipulation leads to hard-coded credentials. This vulnerability is referenced as CVE-2025-4049. The attack can only be performed from a local environment. No exploit is available.
Details
A vulnerability, which was classified as critical, has been found in Signum FARA up to 5.0.80.34. Affected by this issue is an unknown code of the component SQLite Database. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. Using CWE to declare the problem leads to CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Use of hard-coded, the same among all vulnerable installations SQLite credentials vulnerability in SIGNUM-NET FARA allows to read and manipulate local-stored database.This issue affects FARA: through 5.0.80.34.
The weakness was published by Mateusz Sirko. The advisory is available at cert.pl. This vulnerability is handled as CVE-2025-4049 since 04/28/2025. The exploitation is known to be easy. Local access is required to approach this attack. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1110.001 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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-22066). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 5.0.80.0
- 5.0.80.1
- 5.0.80.2
- 5.0.80.3
- 5.0.80.4
- 5.0.80.5
- 5.0.80.6
- 5.0.80.7
- 5.0.80.8
- 5.0.80.9
- 5.0.80.10
- 5.0.80.11
- 5.0.80.12
- 5.0.80.13
- 5.0.80.14
- 5.0.80.15
- 5.0.80.16
- 5.0.80.17
- 5.0.80.18
- 5.0.80.19
- 5.0.80.20
- 5.0.80.21
- 5.0.80.22
- 5.0.80.23
- 5.0.80.24
- 5.0.80.25
- 5.0.80.26
- 5.0.80.27
- 5.0.80.28
- 5.0.80.29
- 5.0.80.30
- 5.0.80.31
- 5.0.80.32
- 5.0.80.33
- 5.0.80.34
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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 credentialsCWE: CWE-798 / CWE-259 / CWE-255
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
04/28/2025 CVE reserved07/21/2025 Advisory disclosed
07/21/2025 VulDB entry created
07/21/2025 VulDB entry last update
Sources
Advisory: cert.plResearcher: Mateusz Sirko
Status: Not defined
CVE: CVE-2025-4049 (🔒)
GCVE (CVE): GCVE-0-2025-4049
GCVE (VulDB): GCVE-100-317090
EUVD: 🔒
Entry
Created: 07/21/2025 11:14Updated: 07/21/2025 16:46
Changes: 07/21/2025 11:14 (66), 07/21/2025 16:46 (1)
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.