How severe is CVE-2014-0177?

CVE-2014-0177 has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-0177?

CVE-2014-0177 affects the following packages: github.com/github/hub (Go), hub (RubyGems). Ecosystems affected: Go, RubyGems.

How do I fix CVE-2014-0177?

Update github.com/github/hub to 1.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0177 is resolved across your whole dependency graph.

How do I detect CVE-2014-0177 in my Go, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/github/hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-0177 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2014-0177 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-0177, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-0177?

CVE-2014-0177 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-0177?

CVE-2014-0177 is classified as CWE-310 (CWE-310). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0177 published, and has it been updated?

CVE-2014-0177 was published on February 15, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go💎 RubyGems

Not in CISA KEV

MEDIUM severity

CVE-2014-0177 — hub

MEDIUMFix: github/hub@016ec99

CVE-2014-0177 is a medium-severity (CVSS 4.4) CWE-310 vulnerability in github.com/github/hub. 1 public exploit reference exists, so weaponization risk is real. A fix is available for github.com/github/hub — see the affected versions and patch details below.

Hub Package Arbitrary File Overwrite

Published

Feb 15, 2022

Updated

Feb 16, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2014-0177 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐹github.com/github/hub💎hub

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, RubyGems packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/github/hub`	all versions	1.12.1`go get github.com/github/hub@v1.12.1`
💎RubyGems	`hub`	all versions	1.12.1`bundle update hub --conservative`

Affected Products

1 product · 1 configurations

Application

hubgithub

≤ 1.12.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The am function in lib/hub/commands.rb in hub before 1.12.1 allows local…

github.comNVDMay 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/github/hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/github/hub to 1.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0177 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2014-0177 in your dependencies?

Find it across Go, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works