lunary-ai lunary up to 1.4.9 API send-verification extractFirstName special elements into a different plane (special element injection)
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in lunary-ai lunary up to 1.4.9. It has been rated as problematic. The affected element is the function extractFirstName of the file /v1/users/send-verification of the component API. Performing a manipulation results in failure to sanitize special elements into a different plane (special element injection).
This vulnerability is reported as CVE-2024-7472. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in lunary-ai lunary up to 1.4.9. This affects the function extractFirstName of the file /v1/users/send-verification of the component API. The manipulation with an unknown input leads to a failure to sanitize special elements into a different plane (special element injection) vulnerability. CWE is classifying the issue as CWE-75. The product does not adequately filter user-controlled input for special elements with control implications. This is going to have an impact on confidentiality. The summary by CVE is:
lunary-ai/lunary v1.2.26 contains an email injection vulnerability in the Send email verification API (/v1/users/send-verification) and Sign up API (/auth/signup). An unauthenticated attacker can inject data into outgoing emails by bypassing the extractFirstName function using a different whitespace character (e.g., \xa0). This vulnerability can be exploited to conduct phishing attacks, damage the application's brand, cause legal and compliance issues, and result in financial impact due to unauthorized email usage.
It is possible to read the advisory at huntr.com. This vulnerability is uniquely identified as CVE-2024-7472 since 08/04/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 1.4.10 eliminates this vulnerability. Applying the patch a39837d7c49936a0c435d241f37ca2ea7904d2cd is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Product: https://github.com/lunary-ai/lunary/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (@huntr_ai): 🔍
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: Failure to sanitize special elements into a different plane (special element injection)CWE: CWE-75 / CWE-707 / CWE-20
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: lunary 1.4.10
Patch: a39837d7c49936a0c435d241f37ca2ea7904d2cd
Timeline
08/04/2024 🔍10/29/2024 🔍
10/29/2024 🔍
11/01/2024 🔍
Sources
Product: github.comAdvisory: huntr.com
Status: Confirmed
CVE: CVE-2024-7472 (🔍)
GCVE (CVE): GCVE-0-2024-7472
GCVE (VulDB): GCVE-100-282387
Entry
Created: 10/29/2024 14:45Updated: 11/01/2024 05:24
Changes: 10/29/2024 14:45 (68), 11/01/2024 05:24 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.