{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12215 is a medium-severity vulnerability in n/a, published on 20 May 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12215 and fix it if it is affected.\n\nWhat it is: CVE-2019-12215 is a medium-severity vulnerability in n/a, published on 20 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-12215 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-2019-12215/ (Markdown: https://insights.sbomify.com/CVE-2019-12215/index.md)","id":"CVE-2019-12215","markdown":"https://insights.sbomify.com/CVE-2019-12215/index.md","name":"CVE-2019-12215","record":{"aliases":["GHSA-pf8r-qgp9-4jg6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Matomo analytics platform","requires_auth":"low_privilege","summary":"An attacker can trigger an error to reveal the full filesystem path of the Matomo installation, aiding further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"matomo","vendor":"matomo"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"A full path disclosure vulnerability was discovered in Matomo v3.9.1 where a user can trigger a particular error to discover the full path of Matomo on the disk, because lastError.file is used in plugins/CorePluginsAdmin/templates/safemode.twig. NOTE: the vendor disputes the significance of this issue, stating \"avoid reporting path disclosures, as we don't consider them as security vulnerabilities.","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-2019-12215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-12216"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-12214"},"products":["n/a"],"published":"2019-05-20","related":[{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2015-7815","kev_date_added":null,"published":"2015-11-16"},{"cvss_score":7.5,"headline":"Deserialization in n/a","id":"CVE-2015-7816","kev_date_added":null,"published":"2015-11-16"},{"cvss_score":7.5,"headline":"Deserialization in n/a","id":"CVE-2009-4137","kev_date_added":null,"published":"2009-12-24"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2009-4140","kev_date_added":null,"published":"2009-12-22"},{"cvss_score":6.8,"headline":"Piwik (now Matomo) Vulnerable to Arbitrary Code Execution","id":"CVE-2011-4941","kev_date_added":null,"published":"2012-09-18"},{"cvss_score":6.8,"headline":"Path traversal in n/a","id":"CVE-2010-2786","kev_date_added":null,"published":"2010-08-02"},{"cvss_score":6.4,"headline":"Security feature bypass in n/a","id":"CVE-2011-0398","kev_date_added":null,"published":"2011-01-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":"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-04","vendors":["n/a"]},"summary":"An attacker can trigger an error to reveal the full filesystem path of the Matomo installation, aiding further attacks.","url":"https://insights.sbomify.com/CVE-2019-12215/"}