Namespace defacement via missing ownership checks
Published Feb 19, 2025 · Updated Feb 19, 2025
Improper authorization in Eclipse Foundation Open VSX 0.9.0 through 0.20.0 allows remote authenticated users to alter namespace details. The updateNamespaceDetails and updateNamespaceDetailsLogo paths passed requests to UserService without identifying the logged-in user or verifying namespace ownership. Any signed-in account can overwrite a namespace's public name, description, website, support and social links, or logo, enabling misleading content and social engineering.
Summary
What happened
Improper authorization in Eclipse Foundation Open VSX 0.9.0 through 0.20.0 allows remote authenticated users to alter namespace details. The updateNamespaceDetails and updateNamespaceDetailsLogo paths passed requests to UserService without identifying the logged-in user or verifying namespace ownership. Any signed-in account can overwrite a namespace's public name, description, website, support and social links, or logo, enabling misleading content and social engineering.
The record
- CVE
- CVE-2025-1007
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- The Eclipse Foundation
- Product
- Open VSX
- Classifications
- CWE-283, CWE-285, T1491.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 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=0.9.0 <=0.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream namespace-details HTTP proof of conceptproof of concept · demonstrated
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