# CVE-2014-5450: Information disclosure in n/a

> Local attackers can read sensitive license files due to world-readable permissions in the Zarafa Collaboration Platform.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vh7c-pr9c-3fgx

## What is CVE-2014-5450?

CVE-2014-5450 is a medium-severity vulnerability in n/a, published on 19 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Zarafa Collaboration Platform 4.1 uses world-readable permissions for /etc/zarafa/license, which allows local users to obtain sensitive information by reading license files.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Zarafa Zarafa Collaboration Platform.

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

Apply the vendor's patch.

## Is CVE-2014-5450 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-3436](https://insights.sbomify.com/CVE-2015-3436/): Path traversal in n/a (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5450 is a medium-severity vulnerability in n/a, published on 19 Mar 2018. 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-5450 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-5450/ (Markdown: https://insights.sbomify.com/CVE-2014-5450/index.md)
```

## Sources

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

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