Authenticated invoice disclosure via unchecked customer identifiers
Published Dec 1, 2021 · Updated Aug 3, 2024
Improper access control in Kimai before 1.16.2 allows remote authenticated users to read unauthorized customer invoice data. The invoice preview and creation routes accepted a customer identifier without checking the account's access to that customer, while form queries could preselect otherwise hidden customer IDs. A low-privileged account with invoice permissions can exploit the flaw over the network to disclose invoice data belonging to customers outside its assigned teams.
Summary
What happened
Improper access control in Kimai before 1.16.2 allows remote authenticated users to read unauthorized customer invoice data. The invoice preview and creation routes accepted a customer identifier without checking the account's access to that customer, while form queries could preselect otherwise hidden customer IDs. A low-privileged account with invoice permissions can exploit the flaw over the network to disclose invoice data belonging to customers outside its assigned teams.
The record
- CVE
- CVE-2021-3992
- Published
- Dec 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Kevin Papst
- Product
- Kimai
- Classifications
- CWE-639, CWE-284, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <1.16.2
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.dev bounty exploit artifactproof 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