Application-limit bypass via unchecked app creation
Published May 24, 2022 · Updated Aug 3, 2024
Business logic error in Erudika Para before 1.45.11 allows remote authenticated users to create applications beyond the configured account limit. The reviewed GitHub advisory says app creation proceeds after the per-user limit is reached, while the cited patch instead adds explicit maximum-password-length validation. Low-privileged access is required; the bounded consequence is unauthorized application creation rather than disclosed data access or service interruption.
Summary
What happened
Business logic error in Erudika Para before 1.45.11 allows remote authenticated users to create applications beyond the configured account limit. The reviewed GitHub advisory says app creation proceeds after the per-user limit is reached, while the cited patch instead adds explicit maximum-password-length validation. Low-privileged access is required; the bounded consequence is unauthorized application creation rather than disclosed data access or service interruption.
The record
- CVE
- CVE-2022-1848
- Published
- May 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Erudika
- Product
- Para
- Classifications
- CWE-840
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 24, 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 <1.45.11
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.
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