{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-28069 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-28069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-28069 is a high-severity vulnerability in n/a, published on 16 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-28069 and fix it if it is affected.\n\nWhat it is: CVE-2024-28069 is a high-severity vulnerability in n/a, published on 16 Mar 2024. 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-2024-28069 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-2024-28069/ (Markdown: https://insights.sbomify.com/CVE-2024-28069/index.md)","id":"CVE-2024-28069","markdown":"https://insights.sbomify.com/CVE-2024-28069/index.md","name":"CVE-2024-28069","record":{"aliases":["GHSA-4qgr-49jh-j3vp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Mitel MiContact Center","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive information and perform unauthorized actions in the legacy chat component due to improper configuration.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"micontact_center_business","vendor":"mitel"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-922","name":"Insecure Storage of Sensitive Information"}],"description":"A vulnerability in the legacy chat component of Mitel MiContact Center Business through 10.0.0.4 could allow an unauthenticated attacker to conduct an information disclosure attack due to improper configuration. A successful exploit could allow an attacker to access sensitive information and potentially conduct unauthorized actions within the vulnerable component.","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-2024-28069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-28070"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2024-28068"},"products":["n/a"],"published":"2024-03-16","related":[{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2023-22854","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2021-3352","kev_date_added":null,"published":"2021-08-13"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2024-42514","kev_date_added":null,"published":"2024-10-01"},{"cvss_score":7.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-24692","kev_date_added":null,"published":"2020-09-25"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2024-28070","kev_date_added":null,"published":"2024-03-16"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2020-9379","kev_date_added":null,"published":"2020-02-25"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["n/a"]},"summary":"Unauthenticated attackers can access sensitive information and perform unauthorized actions in the legacy chat component due to improper configuration.","url":"https://insights.sbomify.com/CVE-2024-28069/"}