# CVE-2014-0177: Hub Package Arbitrary File Overwrite

> Local attackers can overwrite arbitrary files via symlink attacks on temporary patch files in the hub command-line tool.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x5m6-jh4r-34mv, openSUSE-SU-2024:10501-1

## What is CVE-2014-0177?

CVE-2014-0177 is a low-severity path traversal vulnerability in n/a, published on 27 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The am function in lib/hub/commands.rb in hub before 1.12.1 allows local users to overwrite arbitrary files via a symlink attack on a temporary patch file.

Weakness: CWE-310

## Which versions are affected by CVE-2014-0177?

4 open source packages ship an affected version, including github.com/github/hub and hub. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/github/hub` | Go | All versions | 1.12.1 |
| `github.com/github/hub` | Go | All versions | 1.12.1 |
| `hub` | RubyGems | All versions | 1.12.1 |
| `hub` | RubyGems | All versions | 1.12.1 |

Products: Github Hub.

## How do I fix CVE-2014-0177?

Upgrade github.com/github/hub to 1.12.1 or later.

## Is CVE-2014-0177 being exploited?

There is no known exploitation of CVE-2014-0177 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0177 and fix it if it is affected.

What it is: CVE-2014-0177 is a low-severity path traversal vulnerability in n/a, published on 27 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0177 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/github/hub (Go): affected all versions; fixed in 1.12.1
- github.com/github/hub (Go): affected all versions; fixed in 1.12.1
- hub (RubyGems): affected all versions; fixed in 1.12.1
- hub (RubyGems): affected all versions; fixed in 1.12.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0177/ (Markdown: https://insights.sbomify.com/CVE-2014-0177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0177
- OSV: https://osv.dev/vulnerability/CVE-2014-0177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0177/
Summaries are generated and may contain mistakes; the official description above is the record.