{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2013-2786 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-2786 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-2786 is a medium-severity vulnerability in n/a, published on 10 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-2786 and fix it if it is affected.\n\nWhat it is: CVE-2013-2786 is a medium-severity vulnerability in n/a, published on 10 Jul 2013. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-2786 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-2013-2786/ (Markdown: https://insights.sbomify.com/CVE-2013-2786/index.md)","id":"CVE-2013-2786","markdown":"https://insights.sbomify.com/CVE-2013-2786/index.md","name":"CVE-2013-2786","record":{"aliases":["GHSA-j9pj-gj4w-cfc2"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Alstom Grid MiCOM","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by placing a Trojan horse executable in the weakly protected MiCOM S1 installation directory.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"micom_s1_agile","vendor":"alstom"},{"product":"micom_s1_studio","vendor":"alstom"}],"cvss":{"score":6.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:M/Au:S/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Alstom Grid MiCOM S1 Agile before 1.0.3 and Alstom Grid MiCOM S1 Studio use weak permissions for the MiCOM S1 %PROGRAMFILES% directory, which allows local users to gain privileges via a Trojan horse executable file.","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":"Privilege escalation in n/a","id":"CVE-2013-2786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2013"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2013-2787"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2013-2785"},"products":["n/a"],"published":"2013-07-10","related":[],"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-16","vendors":["n/a"]},"summary":"Local attackers can escalate privileges by placing a Trojan horse executable in the weakly protected MiCOM S1 installation directory.","url":"https://insights.sbomify.com/CVE-2013-2786/"}