Cross-organization project renaming via unchecked project ID
Published Apr 16, 2024 · Updated Jan 31, 2025
IDOR in Lunary before 1.0.0 allows remote authenticated users to rename other organizations' projects through the project update API. The PATCH /v1/projects/:projectId endpoint accepts a caller-supplied project ID without verifying that the project belongs to the authenticated user's organization. Any authenticated account that learns another project's ID can alter that project's name, but the documented action does not delete projects or expose their contents.
Summary
What happened
IDOR in Lunary before 1.0.0 allows remote authenticated users to rename other organizations' projects through the project update API. The PATCH /v1/projects/:projectId endpoint accepts a caller-supplied project ID without verifying that the project belongs to the authenticated user's organization. Any authenticated account that learns another project's ID can alter that project's name, but the documented action does not delete projects or expose their contents.
The record
- CVE
- CVE-2024-1626
- Published
- Apr 16, 2024
- Updated
- Jan 31, 2025
- Vendor
- Lunary
- Product
- Lunary
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 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=*
- Affected versionversion=unspecified <1.0.0
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
No public exploit references are available in this record.
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