CVE-2014-2914
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 · uneditedfish (aka fish-shell) 2.0.0 before 2.1.1 does not restrict access to the configuration service (aka fish_config), which allows remote attackers to execute arbitrary code via unspecified vectors, as demonstrated by set_prompt.
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 confidencefish-shell versions 2.0.0 through 2.1.0 contain an unrestricted configuration service (fish_config) that allows remote attackers to execute arbitrary code via unspecified vectors, demonstrated through the set_prompt function. The vulnerability has a critical CVSS score of 9.8 due to the potential for complete system compromise through arbitrary code execution.
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>= 2.0.0, < 2.1.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed fish-shell versionRun 'fish --version' in terminal or check your system package manager for fish-shell package versionAffected if Version is 2.0.0 through 2.1.0 (any version >= 2.0.0 and < 2.1.1)
-
Verify fish_config command exists and is executableRun 'which fish_config' or 'type fish_config' to confirm the fish_config command is available in your installationAffected if fish_config command is present and accessible on the system
-
Test fish_config web interface functionalityExecute 'fish_config' and check if it launches a local web server (typically on localhost:8000) for configurationAffected if fish_config successfully starts the web-based configuration interface
If fish-shell version is 2.0.0 through 2.1.0 AND the fish_config command is accessible/executable, the environment is vulnerable to arbitrary code execution through the configuration service.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped2.1.1
Upgrade fish-shell to version 2.1.1 or later, which contains the fix restricting access to the fish_config service. If immediate upgrade is not possible, disable or restrict network access to fish_config functionality.
fish-shell version 2.1.1 or later
- 1. Check the current fish-shell version by running: fish --version
- 2. If the version is >= 2.0.0 and < 2.1.1, upgrade fish-shell to version 2.1.1 or later
- 3. On Debian/Ubuntu: sudo apt-get update && sudo apt-get install fish
- 4. On Red Hat/CentOS: sudo yum install fish
- 5. On macOS: brew upgrade fish
- 6. Verify the upgrade was successful by running: fish --version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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