Authenticated code execution through read-only sessions
Published May 11, 2021 · Updated Aug 3, 2024
Authorization bypass in JetBrains CodeWithMe before 2021.1 allows remote authenticated users to execute code from read-only sessions. The read-only collaboration permission does not block a connected client from invoking code execution, although JetBrains has not disclosed the responsible check or code path. A client must first join a collaboration session with read-only access; exploitation crosses that role boundary and defeats the intended restriction.
Summary
What happened
Authorization bypass in JetBrains CodeWithMe before 2021.1 allows remote authenticated users to execute code from read-only sessions. The read-only collaboration permission does not block a connected client from invoking code execution, although JetBrains has not disclosed the responsible check or code path. A client must first join a collaboration session with read-only access; exploitation crosses that role boundary and defeats the intended restriction.
The record
- CVE
- CVE-2021-31899
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No sourced classifications are available.
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