{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24082 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-24082 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24082 is a critical unsafe deserialization vulnerability in Pegasystems Pega Infinity, published on 19 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24082 and fix it if it is affected.\n\nWhat it is: CVE-2022-24082 is a critical unsafe deserialization vulnerability in Pegasystems Pega Infinity, published on 19 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-24082 in the wild and no public exploit code.\n\nAffected product: Pegasystems Pega Infinity. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-24082/ (Markdown: https://insights.sbomify.com/CVE-2022-24082/index.md)","id":"CVE-2022-24082","markdown":"https://insights.sbomify.com/CVE-2022-24082/index.md","name":"CVE-2022-24082","record":{"aliases":["GHSA-3crj-j3hg-7v57"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Pega Platform","requires_auth":"none","summary":"Attackers can execute arbitrary code on on-premise Pega Platform installations if the JMX interface is exposed to the internet without proper port filtering.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Pega","cpe":[{"product":"infinity","vendor":"pega"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"If an on-premise installation of the Pega Platform is configured with the port for the JMX interface exposed to the Internet and port filtering is not properly configured, then it may be possible to upload serialized payloads to attack the underlying system. This does not affect systems running on PegaCloud due to its design and architecture.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-03-28","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-03-28","kind":"exploitdb","ref":"51099","stars":null,"title":"Pega Platform 8.1.0 - Remote Code Execution (RCE)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Deserialization in Pega Infinity","id":"CVE-2022-24082","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in Pega Infinity","id":"CVE-2022-24083"},"packages":[],"prev":{"headline":"Privilege escalation in NAVER Cloud Explorer Beta","id":"CVE-2022-24077"},"products":["Pega Infinity"],"published":"2022-07-19","related":[{"cvss_score":9.8,"headline":"Auth bypass in Pega Infinity","id":"CVE-2022-24083","kev_date_added":null,"published":"2022-07-25"},{"cvss_score":9.8,"headline":"Auth bypass in Pega Infinity","id":"CVE-2021-27651","kev_date_added":null,"published":"2021-04-29"},{"cvss_score":9.1,"headline":"Code injection in Pega Infinity","id":"CVE-2024-10094","kev_date_added":null,"published":"2024-11-20"},{"cvss_score":8.8,"headline":"Auth bypass in Pega Infinity","id":"CVE-2021-27654","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":6.6,"headline":"Misconfiguration in Pega Infinity","id":"CVE-2021-27653","kev_date_added":null,"published":"2021-04-01"},{"cvss_score":5.9,"headline":"Cross-site scripting in Pega Infinity","id":"CVE-2024-10716","kev_date_added":null,"published":"2024-12-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Pegasystems"]},"summary":"Attackers can execute arbitrary code on on-premise Pega Platform installations if the JMX interface is exposed to the internet without proper port filtering.","url":"https://insights.sbomify.com/CVE-2022-24082/"}