# CVE-2007-4849: Missing authorization in n/a

> Local users can bypass file permissions on JFFS2 filesystems with POSIX ACLs enabled, potentially accessing or modifying restricted files after a remount.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 12 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ffmh-3m8x-67m8

## What is CVE-2007-4849?

CVE-2007-4849 is a medium-severity missing authorization vulnerability in n/a, published on 12 Sep 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

JFFS2, as used on One Laptop Per Child (OLPC) build 542 and possibly other Linux systems, when POSIX ACL support is enabled, does not properly store permissions during (1) inode creation or (2) ACL setting, which might allow local users to access restricted files or directories after a remount of a filesystem, related to "legacy modes" and an inconsistency between dentry permissions and inode permissions.

Weakness: CWE-264

## Which versions are affected by CVE-2007-4849?

It affects 1 product.


Products: One Laptop per Child Olpc Linux.

## How do I fix CVE-2007-4849?

Apply the vendor's patch.

## Is CVE-2007-4849 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4849 and fix it if it is affected.

What it is: CVE-2007-4849 is a medium-severity missing authorization vulnerability in n/a, published on 12 Sep 2007. 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-2007-4849 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-2007-4849/ (Markdown: https://insights.sbomify.com/CVE-2007-4849/index.md)
```

## Sources

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

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