{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-5067 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-5067 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-5067 is a medium-severity vulnerability in n/a, published on 29 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-5067 and fix it if it is affected.\n\nWhat it is: CVE-2011-5067 is a medium-severity vulnerability in n/a, published on 29 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2011-5067 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-2011-5067/ (Markdown: https://insights.sbomify.com/CVE-2011-5067/index.md)","id":"CVE-2011-5067","markdown":"https://insights.sbomify.com/CVE-2011-5067/index.md","name":"CVE-2011-5067","record":{"aliases":["GHSA-jwm7-r6rr-w9j7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Support Incident Tracker","requires_auth":"low_privilege","summary":"Authenticated users can obtain sensitive installation path information via error messages in Support Incident Tracker.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"support_incident_tracker","vendor":"sitracker"}],"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":"move_uploaded_file.php in Support Incident Tracker (aka SiT!) 3.65 allows remote authenticated users to obtain sensitive information via the file name, which reveals the installation path in an error message.","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-2011-5067","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2011"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2011-5068"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2011-5066"},"products":["n/a"],"published":"2012-01-29","related":[{"cvss_score":10,"headline":"Multiple unspecified vulnerabilities in Salford Software Support Incident Tracker (SiT!) before 3.30 have unknown impact and attack vectors.","id":"CVE-2007-5635","kev_date_added":null,"published":"2007-10-23"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-3831","kev_date_added":null,"published":"2012-01-29"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2011-4337","kev_date_added":null,"published":"2012-01-29"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-5071","kev_date_added":null,"published":"2012-01-29"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-5072","kev_date_added":null,"published":"2012-01-29"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2011-5068","kev_date_added":null,"published":"2012-01-29"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2011-5074","kev_date_added":null,"published":"2012-01-29"}],"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-09-17","vendors":["n/a"]},"summary":"Authenticated users can obtain sensitive installation path information via error messages in Support Incident Tracker.","url":"https://insights.sbomify.com/CVE-2011-5067/"}