CVE-2022-1848: Business Logic Errors in Para

com.erudika:para-core Updated 02 Oct 2025

Summary

25/05/2022
Yes i
Moderate
5.3

CVE-2022-1848: Business Logic Errors in Para. Affects com.erudika:para-core versions < 1.46.0. Fixed in 1.46.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Para is a package in the Maven ecosystem that provides functionality for creating and managing apps. It is used by developers to build applications with user authentication, data storage, and other features. However, prior to version 1.46.0, Para is vulnerable to business logic errors. This vulnerability allows a user to create more than one app, even after reaching the app limit set by the system.

Vulnerability Detail

The vulnerability in Para arises from a flaw in its app creation logic. By exploiting this flaw, a user can bypass the app limit and create multiple apps, potentially leading to resource exhaustion and abuse of system resources. This can impact the stability and performance of the application. The vulnerability has a CVSS score of 5.3, indicating a moderate severity level.

How To Fix

Minimum fixed version

1.46.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to update Para to the fixed version to mitigate the risk.

Conclusion

In conclusion, Para prior to version 1.46.0 is vulnerable to business logic errors that allow users to create more apps than allowed. This can lead to resource exhaustion and abuse of system resources. To mitigate the risk, it is crucial to update Para to version 1.46.0 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.erudika:para-core →

Share this vulnerability

FAQ

Para is a package in the Maven ecosystem that provides functionality for creating and managing apps.

The vulnerability allows users to create more apps than allowed, potentially leading to resource exhaustion and abuse of system resources.

The vulnerability has a CVSS score of 5.3, indicating a moderate severity level.

To fix this vulnerability, update Para to version 1.46.0 or later.

No, there is no known workaround. Updating to the fixed version is necessary.

Related vulnerabilities

Recent vulnerabilities recorded for com.erudika:para-core.

How To Fix

Minimum fixed version

1.46.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback