dbcve.org
S3dvtApplication · S3dvt Project

CVE-2014-1226

HIGH · 7.8 CVSS v3.0 Published 2018-04-06
Fix available
A fix is available. Upgrade to after 0.2.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
The pipe_init_terminal function in main.c in s3dvt allows local users to gain privileges by leveraging setuid permissions and usage of bash 4.3 and earlier. NOTE: This vulnerability exists because of an incomplete fix for CVE-2013-6876.

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

Local privilege escalation vulnerability in the pipe_init_terminal function in s3dvt's main.c. The flaw exists due to an incomplete fix for CVE-2013-6876, where local attackers can exploit setuid permissions combined with bash 4.3 and earlier behavior to gain elevated privileges.

MitigationRemove setuid permissions from the s3dvt binary if not operationally required, or apply any available vendor patches that fully address the bash interaction vulnerability.

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
S3dvtApplication
Affected:<= 0.2.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if s3dvt binary exists
    Run 'which s3dvt' or 'find /usr -name "s3dvt" -type f 2>/dev/null' to locate the binary
    Affected if s3dvt binary is not found on the system (not affected)
  2. Verify s3dvt version
    Run 's3dvt --version' or check the package version with 'dpkg -l | grep s3dvt' or 'rpm -qa | grep s3dvt'
    Affected if Version is 0.2.2 or lower, or version cannot be determined (potentially affected)
  3. Check setuid permissions on s3dvt binary
    Run 'ls -l $(which s3dvt)' and look for 's' in the owner permissions (e.g., -rwsr-xr-x)
    Affected if The binary has setuid bit set (rwsr-xr-x or similar with 's' in owner execute) and is owned by root (likely affected if other conditions met)
  4. Check installed bash version
    Run 'bash --version' and check the first line for version number
    Affected if Bash version is 4.3 or earlier (this condition combined with setuid s3dvt makes exploitation possible)

User is affected if s3dvt version 0.2.2 or lower is installed with setuid permissions AND the system has bash 4.3 or earlier present.

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 a release after 0.2.2
Interim mitigation

Remove setuid permissions from the s3dvt binary if not operationally required, or apply any available vendor patches that fully address the bash interaction vulnerability.

Fix this in S3dvt Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-1226 — 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-1226 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