# CVE-2013-4577: Information disclosure in n/a

> Local attackers can read world-readable GRUB configuration files to obtain password hashes, compromising boot security.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2014
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2013-4577, GHSA-2mm6-f25m-73r7, UBUNTU-CVE-2013-4577

## What is CVE-2013-4577?

CVE-2013-4577 is a low-severity vulnerability in n/a, published on 12 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A certain Debian patch for GNU GRUB uses world-readable permissions for grub.cfg, which allows local users to obtain password hashes, as demonstrated by reading the password_pbkdf2 directive in the file.

Weakness: CWE-264

## Which versions are affected by CVE-2013-4577?

It affects 1 product.


Products: Gnu Grub.

## How do I fix CVE-2013-4577?

Apply the vendor's patch.

## Is CVE-2013-4577 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-4949](https://insights.sbomify.com/CVE-2023-4949/): Memory Corruption Vulnerability in Grub-Legacy's XFS Implementation (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4577 and fix it if it is affected.

What it is: CVE-2013-4577 is a low-severity vulnerability in n/a, published on 12 May 2014. 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-2013-4577 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-2013-4577/ (Markdown: https://insights.sbomify.com/CVE-2013-4577/index.md)
```

## Sources

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

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