Deactivated-account access via inactive-user authentication
Published Apr 25, 2023 · Updated Aug 4, 2024
Improper access control in Odoo Community and Enterprise 13.0 and earlier allows deactivated users to retain RPC access. The core res_users.check method verified and cached a supplied password without first rejecting an account whose active flag was false. Possession of a deactivated account's credentials is required, and successful requests retain that account's ability to read or modify database information.
Summary
What happened
Improper access control in Odoo Community and Enterprise 13.0 and earlier allows deactivated users to retain RPC access. The core res_users.check method verified and cached a supplied password without first rejecting an account whose active flag was false. Possession of a deactivated account's credentials is required, and successful requests retain that account's ability to read or modify database information.
The record
- CVE
- CVE-2021-44460
- Published
- Apr 25, 2023
- Updated
- Aug 4, 2024
- Vendor
- Odoo
- Product
- Odoo Community
- Classifications
- CWE-284, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=0 <=13.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.
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