{"answers":{"affected":"2 open source packages ship an affected version, including tech.powerjob:powerjob. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-36106 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-36106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-36106 is a high-severity vulnerability in n/a, published on 17 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-36106 and fix it if it is affected.\n\nWhat it is: CVE-2023-36106 is a high-severity vulnerability in n/a, published on 17 Aug 2023. 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-2023-36106 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tech.powerjob:powerjob (Maven): affected all versions up to 4.3.2; no fix listed\n- tech.powerjob:powerjob (Maven): affected all versions up to 4.3.2; no fix listed\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-2023-36106/ (Markdown: https://insights.sbomify.com/CVE-2023-36106/index.md)","id":"CVE-2023-36106","markdown":"https://insights.sbomify.com/CVE-2023-36106/index.md","name":"CVE-2023-36106","record":{"aliases":["GHSA-443m-3fr6-w8wj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PowerJob scheduling library","requires_auth":"none","summary":"Remote attackers can obtain sensitive information via the container list interface due to incorrect access control in PowerJob.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"powerjob","vendor":"powerjob"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An incorrect access control vulnerability in powerjob 4.3.2 and earlier allows remote attackers to obtain sensitive information via the interface for querying via appId parameter to /container/list.","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":false,"headline":"PowerJob incorrect access control vulnerability","id":"CVE-2023-36106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-36109"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["4.3.2"],"package":"tech.powerjob:powerjob","purl":null,"source":"GHSA-443m-3fr6-w8wj"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["4.3.2"],"package":"tech.powerjob:powerjob","purl":"pkg:maven/tech.powerjob/powerjob","source":"GHSA-443m-3fr6-w8wj"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-36103"},"products":["n/a"],"published":"2023-08-17","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-44546","kev_date_added":null,"published":"2024-11-11"},{"cvss_score":9.8,"headline":"Code injection in PowerJob","id":"CVE-2023-37754","kev_date_added":null,"published":"2023-07-28"},{"cvss_score":9.8,"headline":"PowerJob vulnerable to incorrect access control","id":"CVE-2023-29924","kev_date_added":null,"published":"2023-04-21"},{"cvss_score":9.8,"headline":"PowerJob vulnerable to remote code execution","id":"CVE-2023-29926","kev_date_added":null,"published":"2023-04-20"},{"cvss_score":7.5,"headline":"Insufficiently Protected Credentials in PowerJob","id":"CVE-2020-28865","kev_date_added":null,"published":"2022-06-16"},{"cvss_score":6.9,"headline":"PowerJob list authorization","id":"CVE-2025-11580","kev_date_added":null,"published":"2025-10-10"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-08","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive information via the container list interface due to incorrect access control in PowerJob.","url":"https://insights.sbomify.com/CVE-2023-36106/"}