# CVE-2014-8327: fal_sftp extension for TYPO3 uses weak permissions for sFTP driver files and folders

> Authenticated users can access sensitive information due to weak file permissions in the TYPO3 sFTP extension.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xwq4-2cwr-fv2q

## What is CVE-2014-8327?

CVE-2014-8327 is a medium-severity vulnerability in n/a, published on 27 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The fal_sftp extension before 0.2.6 for TYPO3 uses weak permissions for sFTP driver files and folders, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

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

4 open source packages ship an affected version, including co-stack/fal_sftp and vertexvaar/falsftp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `co-stack/fal_sftp` | Packagist | All versions | 0.2.6 |
| `co-stack/fal_sftp` | Packagist | All versions | 0.2.6 |
| `vertexvaar/falsftp` | Packagist | All versions | 0.2.6 |
| `vertexvaar/falsftp` | Packagist | All versions | 0.2.6 |

Products: Fal Sftp Project Fal Sftp.

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

Upgrade co-stack/fal_sftp to 0.2.6 or later.

## Is CVE-2014-8327 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8327 is a medium-severity vulnerability in n/a, published on 27 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8327 in the wild and no public exploit code.

Affected packages and fixed versions:
- co-stack/fal_sftp (Packagist): affected all versions; fixed in 0.2.6
- co-stack/fal_sftp (Packagist): affected all versions; fixed in 0.2.6
- vertexvaar/falsftp (Packagist): affected all versions; fixed in 0.2.6
- vertexvaar/falsftp (Packagist): affected all versions; fixed in 0.2.6

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

## Sources

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

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