{"answers":{"affected":"2 open source packages ship an affected version, including com.erudika:para-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1848 in the wild and no public exploit code.","fix":"Upgrade com.erudika:para-core to 1.46.0 or later.","what":"CVE-2022-1848 is a critical vulnerability in erudika/para, published on 24 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-1848 and fix it if it is affected.\n\nWhat it is: CVE-2022-1848 is a critical vulnerability in erudika/para, published on 24 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-1848 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.erudika:para-core (Maven): affected all versions; fixed in 1.46.0\n- com.erudika:para-core (Maven): affected all versions; fixed in 1.46.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-1848/ (Markdown: https://insights.sbomify.com/CVE-2022-1848/index.md)","id":"CVE-2022-1848","markdown":"https://insights.sbomify.com/CVE-2022-1848/index.md","name":"CVE-2022-1848","record":{"aliases":["GHSA-4793-8wwh-jxxr"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Para backend server","requires_auth":"low_privilege","summary":"Attackers can exploit business logic errors in the Para backend server to bypass intended application workflows.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"para","vendor":"erudika"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-840","name":null}],"description":"Business Logic Errors in GitHub repository erudika/para prior to 1.45.11.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Business Logic Errors in erudika/para","id":"CVE-2022-1848","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Session Fixation in filegator/filegator","id":"CVE-2022-1849"},"packages":[{"ecosystem":"Maven","fixed":["1.46.0"],"introduced":["0"],"last_affected":[],"package":"com.erudika:para-core","purl":null,"source":"GHSA-4793-8wwh-jxxr"},{"ecosystem":"Maven","fixed":["1.46.0"],"introduced":["0"],"last_affected":[],"package":"com.erudika:para-core","purl":"pkg:maven/com.erudika/para-core","source":"GHSA-4793-8wwh-jxxr"}],"prev":{"headline":"Rotating Posts \u003c= 1.11 - Arbitrary Settings Update to Stored XSS via CSRF","id":"CVE-2022-1847"},"products":["erudika/para"],"published":"2022-05-24","related":[{"cvss_score":9.4,"headline":"Cross-site Scripting (XSS) - Generic in erudika/para","id":"CVE-2022-1782","kev_date_added":null,"published":"2022-05-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["erudika"]},"summary":"Attackers can exploit business logic errors in the Para backend server to bypass intended application workflows.","url":"https://insights.sbomify.com/CVE-2022-1848/"}