{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-12419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-12419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-12419 is a medium-severity vulnerability in Mantisbt Mantisbt, published on 5 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-12419 and fix it if it is affected.\n\nWhat it is: CVE-2017-12419 is a medium-severity vulnerability in Mantisbt Mantisbt, published on 5 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-12419 in the wild and no public exploit code.\n\nAffected product: Mantisbt Mantisbt. 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-2017-12419/ (Markdown: https://insights.sbomify.com/CVE-2017-12419/index.md)","id":"CVE-2017-12419","markdown":"https://insights.sbomify.com/CVE-2017-12419/index.md","name":"CVE-2017-12419","record":{"aliases":["GHSA-h6vg-jrj8-p6w5"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"MantisBT bug tracker","requires_auth":"high_privilege","summary":"Attackers can read server files if the admin directory is not removed and MySQL local_infile is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mantisbt","vendor":"mantisbt"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"If, after successful installation of MantisBT through 2.5.2 on MySQL/MariaDB, the administrator does not remove the 'admin' directory (as recommended in the \"Post-installation and upgrade tasks\" section of the MantisBT Admin Guide), and the MySQL client has a local_infile setting enabled (in php.ini mysqli.allow_local_infile, or the MySQL client config file, depending on the PHP setup), an attacker may take advantage of MySQL's \"connect file read\" feature to remotely access files on the MantisBT server.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2017-12419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mantisbt:mantisbt","products":["mantisbt:mantisbt"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-12420"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-12418"},"products":["n/a"],"published":"2017-08-05","related":[{"cvss_score":9.6,"headline":"MantisBT allows cross-site scripting (XSS) via crafted filename","id":"CVE-2019-15074","kev_date_added":null,"published":"2019-08-21"},{"cvss_score":9.3,"headline":"MantisBT SOAP API has an authentication bypass vulnerability on MySQL","id":"CVE-2026-30849","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.8,"headline":"MantisBT: Authentication bypass for some passwords due to PHP type juggling","id":"CVE-2025-47776","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.8,"headline":"MantisBT allows arbitrary password reset","id":"CVE-2017-7615","kev_date_added":null,"published":"2017-04-16"},{"cvss_score":8.6,"headline":"MantisBT Vulnerable to Stored HTML Injection in Tag Delete Confirmation","id":"CVE-2026-33517","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.6,"headline":"MantisBT has Stored HTML Injection / XSS when displaying Tags in Timeline","id":"CVE-2026-33548","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.3,"headline":"MantisBT Host Header Injection vulnerability","id":"CVE-2024-23830","kev_date_added":null,"published":"2024-02-20"}],"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-05","vendors":["n/a"]},"summary":"Attackers can read server files if the admin directory is not removed and MySQL local_infile is enabled.","url":"https://insights.sbomify.com/CVE-2017-12419/"}