{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-0927 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-0927 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-0927 is a high-severity path traversal vulnerability in Google Chrome Os, published on 10 Apr 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-0927 and fix it if it is affected.\n\nWhat it is: CVE-2013-0927 is a high-severity path traversal vulnerability in Google Chrome Os, published on 10 Apr 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-0927 in the wild and no public exploit code.\n\nAffected product: Google Chrome Os. 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-0927/ (Markdown: https://insights.sbomify.com/CVE-2013-0927/index.md)","id":"CVE-2013-0927","markdown":"https://insights.sbomify.com/CVE-2013-0927/index.md","name":"CVE-2013-0927","record":{"aliases":["GHSA-cp8g-g2cj-x6hm"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Chrome OS","requires_auth":"none","summary":"Attackers can bypass access restrictions in Chrome OS by exploiting Pango configuration file loading via crafted data or environment variables.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome_os","vendor":"google"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Google Chrome OS before 26.0.1410.57 relies on a Pango pango-utils.c read_config implementation that loads the contents of the .pangorc file in the user's home directory, and the file referenced by the PANGO_RC_FILE environment variable, which allows attackers to bypass intended access restrictions via crafted configuration data.","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":"Path traversal in n/a","id":"CVE-2013-0927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome_os","products":["google:chrome_os"],"type":"path_traversal","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2013-0928"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2013-0926"},"products":["n/a"],"published":"2013-04-10","related":[{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2014-1708","kev_date_added":null,"published":"2014-03-16"},{"cvss_score":10,"headline":"Use after free in n/a","id":"CVE-2013-2833","kev_date_added":null,"published":"2013-04-16"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2013-0915","kev_date_added":null,"published":"2013-03-18"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2864","kev_date_added":null,"published":"2012-08-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2012-4050","kev_date_added":null,"published":"2012-07-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-2171","kev_date_added":null,"published":"2011-05-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-1306","kev_date_added":null,"published":"2011-03-08"}],"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":"Attackers can bypass access restrictions in Chrome OS by exploiting Pango configuration file loading via crafted data or environment variables.","url":"https://insights.sbomify.com/CVE-2013-0927/"}