# CVE-2011-3177: Information disclosure in n/a

> Local attackers can read sensitive network configuration data, such as wireless passwords, due to world-readable file permissions in YaST2.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 8 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x4m3-94qr-f6c3, openSUSE-SU-2024:10410-1

## What is CVE-2011-3177?

CVE-2011-3177 is a high-severity vulnerability in n/a, published on 8 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The YaST2 network created files with world readable permissions which could have allowed local users to read sensitive material out of network configuration files, like passwords for wireless networks.

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

## Which versions are affected by CVE-2011-3177?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2` | openSUSE:Tumbleweed | All versions | 3.2.7-1.1 |

Products: Yast Yast2.

## How do I fix CVE-2011-3177?

Apply the vendor's patch.

## Is CVE-2011-3177 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3177 and fix it if it is affected.

What it is: CVE-2011-3177 is a high-severity vulnerability in n/a, published on 8 Sep 2017. 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-2011-3177 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-2011-3177/ (Markdown: https://insights.sbomify.com/CVE-2011-3177/index.md)
```

## Sources

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

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