CVE-2011-3177

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-17. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 8, 2017

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated Sep 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
GitHub commit

commit 7fe2e3df308b (yast/yast-core)

Fix landed in yast/yast-core commit 7fe2e3df308b — awaiting tagged release

https://github.com/yast/yast-core/commit/7fe2e3df308b8b6a901cb2cfd60f398df53219de
Web page

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=713661

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 20× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 78 of 117 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 22 repeat rows among the latest 100 are merged into the row they repeat. The 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:42 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-07 23:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-06 15:10 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-04 23:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-09-30 14:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-09-29 08:21 UTCEG score recompute
  12. 2026-09-28 13:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-09-27 13:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-09-26 15:52 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-24 13:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-09-20 20:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-09-16 13:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-09-15 03:04 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-09-13 16:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-09-12 14:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-09-06 13:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-09-05 15:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-09-04 13:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-08-25 13:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-08-19 16:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
Show 53 more
  1. 2026-08-18 13:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-08-15 01:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-08-09 13:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-08-06 13:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-08-05 19:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-08-04 15:04 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-08-01 04:10 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-07-30 01:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-07-23 14:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-07-23 01:05 UTCEG score recompute
  11. 2026-07-23 00:09 UTCEG score recompute
  12. 2026-07-22 21:47 UTCEG score recompute
  13. 2026-07-22 14:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-07-21 15:21 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-07-20 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-07-19 02:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-07-18 10:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-07-16 16:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-07-15 16:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-07-15 01:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-07-13 22:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-07-13 06:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-07-11 08:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-07-08 15:10 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-07-06 16:23 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  26. 2026-07-06 02:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  27. 2026-07-05 02:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-07-02 14:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  29. 2026-07-01 15:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  30. 2026-06-30 23:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  31. 2026-06-29 14:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  32. 2026-06-28 14:03 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  33. 2026-06-28 04:52 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  34. 2026-06-27 03:05 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  35. 2026-06-25 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  36. 2026-06-24 14:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  37. 2026-06-23 21:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  38. 2026-06-22 14:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  39. 2026-06-21 01:56 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-06-19 19:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-06-18 17:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-06-17 17:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-06-16 17:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-06-15 17:44 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-06-14 23:14 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  46. 2026-06-13 22:57 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  47. 2026-06-12 23:08 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  48. 2026-06-11 13:56 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  49. 2026-06-10 22:14 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  50. 2026-06-10 13:17 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  51. 2026-06-08 14:14 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  52. 2026-06-07 15:22 UTCEPSS rescoreEPSS <0.1% · 10th percentile
  53. 2026-06-06 13:45 UTCEPSS rescoreEPSS <0.1% · 10th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2011-3177?
CVE-2011-3177 is a high-severity vulnerability; its CVE record was published on September 8, 2017. 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.
When was CVE-2011-3177 made public?
CVE-2011-3177 was made public on March 10, 2017: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 8, 2017. EchelonGraph's copy of the record carries a last-modified date of June 16, 2026; the record at its source may have been updated since.
Is CVE-2011-3177 actively exploited?
CVE-2011-3177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2011-3177?
CVE-2011-3177 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2011-3177?
An upstream fix for CVE-2011-3177 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-3177

Explore →

Is Your Infrastructure Affected by CVE-2011-3177?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs