{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-3293 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-3293 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-3293 is a medium-severity vulnerability in n/a, published on 14 Apr 2015. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-3293 and fix it if it is affected.\n\nWhat it is: CVE-2015-3293 is a medium-severity vulnerability in n/a, published on 14 Apr 2015. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-3293 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-2015-3293/ (Markdown: https://insights.sbomify.com/CVE-2015-3293/index.md)","id":"CVE-2015-3293","markdown":"https://insights.sbomify.com/CVE-2015-3293/index.md","name":"CVE-2015-3293","record":{"aliases":["GHSA-2fg2-cvw6-w6w2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FortiMail email security","requires_auth":"high_privilege","summary":"Remote administrators can obtain credentials via a debug command, exposing sensitive information in FortiMail email security appliances.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fortimail","vendor":"fortinet"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"FortiMail 5.0.3 through 5.2.3 allows remote administrators to obtain credentials via the \"diag debug application httpd\" command.","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-2015-3293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-3294"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2015-3292"},"products":["n/a"],"published":"2015-04-14","related":[{"cvss_score":9.8,"headline":"Fortinet FortiMail Path Traversal","id":"CVE-2026-104286","kev_date_added":"2026-10-01","published":"2026-10-01"},{"cvss_score":9.8,"headline":"Auth bypass in Fortinet FortiMail","id":"CVE-2021-36166","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":9.8,"headline":"SQL injection in Fortinet FortiMail","id":"CVE-2021-24007","kev_date_added":null,"published":"2021-07-09"},{"cvss_score":9.8,"headline":"Auth bypass in FortiMail","id":"CVE-2020-9294","kev_date_added":null,"published":"2020-04-27"},{"cvss_score":9,"headline":"Auth bypass in FortiMail","id":"CVE-2023-47539","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":8.8,"headline":"Path traversal in Fortinet FortiMail","id":"CVE-2021-24013","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":8.8,"headline":"Memory corruption in Fortinet FortiMail","id":"CVE-2021-22129","kev_date_added":null,"published":"2021-07-09"}],"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-06","vendors":["n/a"]},"summary":"Remote administrators can obtain credentials via a debug command, exposing sensitive information in FortiMail email security appliances.","url":"https://insights.sbomify.com/CVE-2015-3293/"}