{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-1422 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-1422 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-1422 is a medium-severity vulnerability in Canonical trust-store (Ubuntu RTM), published on 22 Jul 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2014-1422 and fix it if it is affected.\n\nWhat it is: CVE-2014-1422 is a medium-severity vulnerability in Canonical trust-store (Ubuntu RTM), published on 22 Jul 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2014-1422 in the wild and no public exploit code.\n\nAffected product: Canonical trust-store (Ubuntu RTM). 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-2014-1422/ (Markdown: https://insights.sbomify.com/CVE-2014-1422/index.md)","id":"CVE-2014-1422","markdown":"https://insights.sbomify.com/CVE-2014-1422/index.md","name":"CVE-2014-1422","record":{"aliases":["GHSA-hm2r-m89c-6rgm"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ubuntu trust-store","requires_auth":"low_privilege","summary":"Applications retain location access after user revocation due to cached permissions, bypassing privacy controls in Ubuntu's trust-store.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"trust-store_\\(ubuntu\\)","vendor":"canonical"},{"product":"trust-store_\\(ubuntu_rtm\\)","vendor":"canonical"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-275","name":null}],"description":"In Ubuntu's trust-store, if a user revokes location access from an application, the location is still available to the application because the application will honour incorrect, cached permissions. This is because the cache was not ordered by creation time by the Select struct in src/core/trust/impl/sqlite3/store.cpp. Fixed in trust-store (Ubuntu) version 1.1.0+15.04.20150123-0ubuntu1 and trust-store (Ubuntu RTM) version 1.1.0+15.04.20150123~rtm-0ubuntu1.","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":"Location service uses cached authorization even after revocation","id":"CVE-2014-1422","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Online Accounts Signon daemon gives out all oauth tokens to any app","id":"CVE-2014-1423"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2014-1421"},"products":["trust-store (Ubuntu RTM)","trust-store (Ubuntu)"],"published":"2020-07-22","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-17","vendors":["Canonical"]},"summary":"Applications retain location access after user revocation due to cached permissions, bypassing privacy controls in Ubuntu's trust-store.","url":"https://insights.sbomify.com/CVE-2014-1422/"}