LiveActive security incident?Get immediate response
CVE Record

CVE-2014-1422: Location service uses cached authorization even after revocation

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.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw could let an Ubuntu application keep receiving location data after a user revoked that permission. Business impact is privacy exposure rather than system takeover. The issue is fixed in named Canonical trust-store package versions, and no provided source indicates active exploitation.

Executive priority

Treat as a moderate privacy-risk issue. It is most urgent for products or managed devices where location privacy is regulated, contractual, or customer-facing. Patch validation should be scheduled, but the sources do not support emergency exploitation claims.

Technical view

Ubuntu trust-store cached authorization results incorrectly because Select in src/core/trust/impl/sqlite3/store.cpp did not order cache entries by creation time. A stale location permission decision could be honored after revocation, allowing continued location access. CVSS is 5.0 with local access, low complexity, low privileges, user interaction, and high confidentiality impact.

Likely exposure

Exposure appears limited to systems using affected Canonical trust-store 1.1.0 or Ubuntu RTM trust-store 1.1.0 for application location authorization.

Exploitation context

The provided data does not show KEV listing or active exploitation. Abuse would require a local application context and a permission state where location access was revoked but stale cached authorization remained effective.

Researcher notes

Focus validation on stale authorization decisions after revocation, not code execution. The root cause is cache selection ordering in the sqlite3 trust-store implementation. Evidence is specific to location permission handling and the two Canonical package tracks named in the CVE data.

Mitigation direction

  • Upgrade Ubuntu trust-store to 1.1.0+15.04.20150123-0ubuntu1 or later.
  • Upgrade Ubuntu RTM trust-store to 1.1.0+15.04.20150123~rtm-0ubuntu1 or later.
  • Check Canonical guidance for applicable backported packages or supported release handling.
  • Prioritize devices or images that expose location services to third-party applications.

Validation and detection

  • Inventory installed trust-store package versions on relevant Ubuntu or Ubuntu RTM systems.
  • Confirm the installed package is at or above the fixed version named by Canonical.
  • Review application permission revocation behavior for location-sensitive deployments.
  • Check whether affected devices still run obsolete Ubuntu trust-store builds.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-275: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-1422 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N1.33.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5Medium
CVSS 3.1 vector shape for CVE-2014-1422Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Canonicaltrust-store (Ubuntu)1.1.0Listed
Canonicaltrust-store (Ubuntu RTM)1.1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-275 · source CWE mapping

Permission Issues

Permission Issues represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.