| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in REDCap 14.3.13. Affected by this issue is some unknown functionality of the component Login. Performing a manipulation results in response discrepancy. This vulnerability is reported as CVE-2024-55374. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in REDCap 14.3.13. This affects an unknown functionality of the component Login. The manipulation with an unknown input leads to a response discrepancy vulnerability. CWE is classifying the issue as CWE-204. The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere. This is going to have an impact on confidentiality. The summary by CVE is:
REDCap 14.3.13 allows an attacker to enumerate usernames due to an observable discrepancy between login attempts.
This vulnerability is uniquely identified as CVE-2024-55374 since 12/06/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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: Response discrepancyCWE: CWE-204 / CWE-203 / CWE-200
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
12/06/2024 CVE reserved01/02/2026 Advisory disclosed
01/02/2026 VulDB entry created
01/02/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2024-55374 (🔒)
GCVE (CVE): GCVE-0-2024-55374
GCVE (VulDB): GCVE-100-339417
Entry
Created: 01/02/2026 16:48Changes: 01/02/2026 16:48 (51)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.