# CVE-2020-12831: Information disclosure in n/a

> An attacker can read sensitive configuration data because the init script creates world-readable files when the split-config feature is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** Yes
- **Published:** 13 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALSA-2020:4619, DEBIAN-CVE-2020-12831, GHSA-x83m-q23q-xv5j, RHSA-2020:4619, openSUSE-SU-2024:10583-1

## What is CVE-2020-12831?

CVE-2020-12831 is a medium-severity vulnerability in n/a, published on 13 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in FRRouting FRR (aka Free Range Routing) through 7.3.1. When using the split-config feature, the init script creates an empty config file with world-readable default permissions, leading to a possible information leak via tools/frr.in and tools/frrcommon.sh.in. NOTE: some parties consider this user error, not a vulnerability, because the permissions are under the control of the user before any sensitive information is present in the file

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2020-12831?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr-contrib` | AlmaLinux:8 | All versions | 7.0-10.el8 |
| `frr` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.0-10.el8 |
| `frr-contrib` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.0-10.el8 |
| `frr-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.0-10.el8 |
| `frr-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:7.0-10.el8 |
| `frr` | openSUSE:Tumbleweed | All versions | 7.5.1-3.1 |

Products: Linuxfoundation Free Range Routing.

## How do I fix CVE-2020-12831?

Apply the vendor's patch.

## Is CVE-2020-12831 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12831 and fix it if it is affected.

What it is: CVE-2020-12831 is a medium-severity vulnerability in n/a, published on 13 May 2020. 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-2020-12831 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-2020-12831/ (Markdown: https://insights.sbomify.com/CVE-2020-12831/index.md)
```

## Sources

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

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