{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11533 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11533 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11533 is a medium-severity vulnerability in n/a, published on 4 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11533 and fix it if it is affected.\n\nWhat it is: CVE-2020-11533 is a medium-severity vulnerability in n/a, published on 4 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-11533 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-2020-11533/ (Markdown: https://insights.sbomify.com/CVE-2020-11533/index.md)","id":"CVE-2020-11533","markdown":"https://insights.sbomify.com/CVE-2020-11533/index.md","name":"CVE-2020-11533","record":{"aliases":["GHSA-rj9w-gh2x-8hf5"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Ivanti Workspace Control","requires_auth":"low_privilege","summary":"Local attackers can obtain sensitive keying material when SCCM integration is enabled in Ivanti Workspace Control.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"workspace_control","vendor":"ivanti"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Ivanti Workspace Control before 10.4.30.0, when SCCM integration is enabled, allows local users to obtain sensitive information (keying material).","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":"Information disclosure in n/a","id":"CVE-2020-11533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2020-11534"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-11532"},"products":["n/a"],"published":"2020-04-04","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-16382","kev_date_added":null,"published":"2020-03-19"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Workspace Control","id":"CVE-2025-22455","kev_date_added":null,"published":"2025-06-10"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Workspace Control","id":"CVE-2025-5353","kev_date_added":null,"published":"2025-06-10"},{"cvss_score":8.8,"headline":"Privilege escalation in Workspace Control","id":"CVE-2024-44103","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":8.8,"headline":"Auth bypass in Workspace Control","id":"CVE-2024-44104","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":8.8,"headline":"Privilege escalation in Workspace Control","id":"CVE-2024-44106","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":8.8,"headline":"Privilege escalation in Workspace Control","id":"CVE-2024-44107","kev_date_added":null,"published":"2024-09-10"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Local attackers can obtain sensitive keying material when SCCM integration is enabled in Ivanti Workspace Control.","url":"https://insights.sbomify.com/CVE-2020-11533/"}