CVE-2017-15918: Sera 1.2 stores the user's login password in plain text in their home directory

This month

HIGH 7.8DOWNGRADEDOWNGRADE

CVE-2017-15918 is a high-severity flaw (CVSS 7.8) affecting sera, sera. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Sera 1.2 stores the user's login password in plain text in their home directory. This makes privilege escalation trivial and also exposes the user and system keychains to local attacks.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.2% (top 33%)
CISA exploited list	No
Weakness	CWE-522
Published	2017-11-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: ignitum

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-11-01 17:29 UTCPublished CVE record published
2026-06-17 01:08 UTCUpdated Record last modified

ignitum sera DOWNGRADE

Affected: 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy sera || rpm -q sera || sera --version

2. No fixed release: DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison sera sudo apt install sera=<VERSION_BEFORE_1.2> sudo apt-mark hold sera

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sera sudo dnf downgrade sera-<VERSION_BEFORE_1.2> sudo dnf versionlock add sera

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

ignitum sera DOWNGRADE

Affected: 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy sera || rpm -q sera || sera --version

2. No fixed release: DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison sera sudo apt install sera=<VERSION_BEFORE_1.2> sudo apt-mark hold sera

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sera sudo dnf downgrade sera-<VERSION_BEFORE_1.2> sudo dnf versionlock add sera

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Sera 1.2 - Local Privilege Escalation / Password Disclosure

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-15918?

sera: downgrade or apply the listed mitigation; sera: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-15918 being exploited?

CVE-2017-15918 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-15918 affect?

CVE-2017-15918 affects sera, sera. Severity is high (CVSS 7.8). Sera 1.2 stores the user's login password in plain text in their home directory. This makes privilege escalation trivial and also exposes the user and system keychains to local attacks.

How urgent is CVE-2017-15918?

Priority 49/100. High severity; Public exploit reference

References

← Back to latest CVEs