The skyring-setup command creates random password for mongodb skyring database but it writes password in plain text to /etc/skyring/skyring…

published 2018-07-06 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11812

cvss: 4.8; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits: 0; none known

The skyring-setup command creates random password for mongodb skyring database but it writes password in plain text to /etc/skyring/skyring.conf file which is owned by root but read by local user. Any local user who has access to system running skyring service will be able to get password in plain text.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2665 updated 2026-06-30 cvss 4.8

rhscon-core: creates world readable file /etc/skyring/skyring.conf which leaks mongodb password for skyring database

Red Hat Storage Console 2 rhscon-core
affected: workaround, no fix planned “~]# chmod 600 /etc/skyring/skyring.conf”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.0	4.8	CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
NVD	3.0	7.0	CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	1.9	AV:L/AC:M/Au:N/C:P/I:N/A:N

Affected products

[UNKNOWN] rhscon-core

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

Technology feeds

MongoDB rss critical rss

References

securityfocus.com /bid/97612
vdb-entry, third-party-advisory
bugzilla.redhat.com /show_bug.cgi?id=CVE-2017-2665
issue-tracking, third-party-advisory

Sources

CVE List CVE-2017-2665
NVD CVE-2017-2665

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary