Unauthenticated backend access via crafted cookie
Published May 26, 2022 · Updated Aug 3, 2024
Improper access control in Linglong 1.0 allows remote attackers to enter the administrative backend through a crafted cookie. The public record identifies cookie handling as the locus but does not disclose which cookie field is trusted or how its value bypasses authorization. No authentication or user interaction is required, but public sources do not identify the exposed backend functions or confirm impacts beyond unauthorized backend access.
Summary
What happened
Improper access control in Linglong 1.0 allows remote attackers to enter the administrative backend through a crafted cookie. The public record identifies cookie handling as the locus but does not disclose which cookie field is trusted or how its value bypasses authorization. No authentication or user interaction is required, but public sources do not identify the exposed backend functions or confirm impacts beyond unauthorized backend access.
The record
- CVE
- CVE-2022-29633
- Published
- May 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 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?
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
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