API credential acquisition via cookie-authenticated regeneration
Published Feb 26, 2022 · Updated Aug 3, 2024
Improper access control in Zulip Server before 4.10 allows remote attackers with a valid session cookie to obtain a replacement API key. The API-key regeneration handler was registered under the cookie-authenticated web namespace, allowing a logged-in browser session to invoke the handler without presenting the existing API key. A valid browser session was the only gate; successful exploitation returned a new persistent API credential and invalidated the previous key.
Summary
What happened
Improper access control in Zulip Server before 4.10 allows remote attackers with a valid session cookie to obtain a replacement API key. The API-key regeneration handler was registered under the cookie-authenticated web namespace, allowing a logged-in browser session to invoke the handler without presenting the existing API key. A valid browser session was the only gate; successful exploitation returned a new persistent API credential and invalidated the previous key.
The record
- CVE
- CVE-2021-3967
- Published
- Feb 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Zulip
- Product
- Zulip Server
- Classifications
- CWE-284, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2022CVE 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 <4.10
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
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