dbcve.org
SignondApplication · Signond Project

CVE-2014-1423

MEDIUM · 5.5 CVSS v3.1 Published 2020-05-07
Fix available
A fix is available. Upgrade to 8.57 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
signond before 8.57+15.04.20141127.1-0ubuntu1, as used in Ubuntu Touch, did not properly restrict applications from querying oath tokens due to incorrect checks and the missing installation of the signon-apparmor-extension. An attacker could use this create a malicious click app that collects oauth tokens for other applications, exposing sensitive information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The signond (sign-on daemon) in Ubuntu Touch versions before 8.57+15.04.20141127.1-0ubuntu1 contained improper access controls that allowed applications to query OATH tokens belonging to other applications. This was due to incorrect permission checks in the daemon and the absence of the signon-apparmor-extension package, which should enforce AppArmor confinement between applications.

MitigationUpgrade signond to version 8.57+15.04.20141127.1-0ubuntu1 or later and ensure the signon-apparmor-extension is installed to enforce proper AppArmor isolation between applications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SignondApplication
Affected:< 8.57\+15.04.20141127.1-0ubuntu1
Ubuntu TouchApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check signond version
    Run 'dpkg -l signond' or 'apt policy signond' to retrieve the installed package version
    Affected if The installed version is lower than 8.57+15.04.20141127.1-0ubuntu1
  2. Check signon-apparmor-extension installation
    Run 'dpkg -l signon-apparmor-extension' to verify whether the package is installed
    Affected if The package is not installed (not present in dpkg output)
  3. Verify AppArmor extension status
    Query the package manager for signon-apparmor-extension details using 'apt-cache policy signon-apparmor-extension'
    Affected if The package shows as 'not installed' or 'not installed yet'

You are affected if signond version is below 8.57+15.04.20141127.1-0ubuntu1 OR if the signon-apparmor-extension package is not installed, as both conditions enable the improper token access vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 8.57 or later
Fixed in 8.57
Interim mitigation

Upgrade signond to version 8.57+15.04.20141127.1-0ubuntu1 or later and ensure the signon-apparmor-extension is installed to enforce proper AppArmor isolation between applications.

Fix this in Signond Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1423 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data