Authenticated tag creation via permissive default rank
Published Aug 3, 2023 · Updated Oct 10, 2024
Missing authorization in Apache Answer before 1.1.1 allows remote authenticated users to create tags without the intended reputation. During database initialization, rank.tag.add is set to 1 and the intended medium default privilege profile is not persisted, so any registered account meets the tag-creation threshold. The flaw requires a logged-in account and permits unauthorized tag creation, an integrity impact confined to community taxonomy rather than service availability.
Summary
What happened
Missing authorization in Apache Answer before 1.1.1 allows remote authenticated users to create tags without the intended reputation. During database initialization, rank.tag.add is set to 1 and the intended medium default privilege profile is not persisted, so any registered account meets the tag-creation threshold. The flaw requires a logged-in account and permits unauthorized tag creation, an integrity impact confined to community taxonomy rather than service availability.
The record
- CVE
- CVE-2023-4124
- Published
- Aug 3, 2023
- Updated
- Oct 10, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Answer
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2023CVE publishedPublication date reported by the CVE source.
- Oct 10, 2024Record 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=unspecified <v1.1.1
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.
Public exploit references
- huntr proof of concept for Answer missing authorizationproof 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