{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36170 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36170 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36170 is a high-severity vulnerability in n/a, published on 19 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36170 and fix it if it is affected.\n\nWhat it is: CVE-2022-36170 is a high-severity vulnerability in n/a, published on 19 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36170 in the wild and no public exploit code.\n\nAffected product: n/a. 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-36170/ (Markdown: https://insights.sbomify.com/CVE-2022-36170/index.md)","id":"CVE-2022-36170","markdown":"https://insights.sbomify.com/CVE-2022-36170/index.md","name":"CVE-2022-36170","record":{"aliases":["GHSA-4586-3c3g-jv96"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MapGIS IGServer","requires_auth":"low_privilege","summary":"Hardcoded credentials in MapGIS IGServer allow attackers to escalate privileges and delete arbitrary files.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"igserver","vendor":"mapgis"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"MapGIS 10.5 Pro IGServer has hardcoded credentials in the front-end and can lead to escalation of privileges and arbitrary file deletion.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-36170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-36171"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2022-36168"},"products":["n/a"],"published":"2022-08-19","related":[],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Hardcoded credentials in MapGIS IGServer allow attackers to escalate privileges and delete arbitrary files.","url":"https://insights.sbomify.com/CVE-2022-36170/"}