Authenticated project renaming via missing access check
Published May 21, 2024 · Updated Jan 31, 2025
Incorrect authorization in Lunary before 1.2.26 allows remote authenticated users to rename projects outside their access. The project-update PATCH endpoint accepts a caller-supplied project identifier and persists a new name without verifying project assignment. Any unprivileged account can alter another project's stored name, affecting project-data integrity without reported deletion or service interruption.
Summary
What happened
Incorrect authorization in Lunary before 1.2.26 allows remote authenticated users to rename projects outside their access. The project-update PATCH endpoint accepts a caller-supplied project identifier and persists a new name without verifying project assignment. Any unprivileged account can alter another project's stored name, affecting project-data integrity without reported deletion or service interruption.
The record
- CVE
- CVE-2024-4154
- Published
- May 21, 2024
- Updated
- Jan 31, 2025
- Vendor
- Lunary
- Product
- Lunary
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- Jan 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.2
- Affected versionversion=unspecified <1.2.26
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr proof-of-concept requestproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo