# CVE-2014-5179: Missing authorization in n/a

> Remote attackers can obtain sensitive node and user information due to missing access permission checks in the Drupal freelinking module.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-68qr-46rm-f7wh

## What is CVE-2014-5179?

CVE-2014-5179 is a medium-severity missing authorization vulnerability in n/a, published on 6 Aug 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The freelinking module for Drupal, as used in the Freelinking for Case Tracker module, does not properly check access permissions for (1) nodes or (2) users, which allows remote attackers to obtain sensitive information via a crafted link.

Weakness: CWE-264

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

It affects 2 products.


Products: Freelinking for Case Tracker Project Freelinking for Case Tracker, Freelinking Project Freelinking.

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

No fix has been published for CVE-2014-5179 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-5179 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5179 is a medium-severity missing authorization vulnerability in n/a, published on 6 Aug 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-5179 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-5179/ (Markdown: https://insights.sbomify.com/CVE-2014-5179/index.md)
```

## Sources

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

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