CVE-2015-2204: Evergreen before 2.5.9, 2.6.x before 2.6.7, and 2.7.x before 2.7.4 allows remote attackers to bypass an intend

This month

HIGH 7.5REMOTEUPGRADE

CVE-2015-2204 is a high-severity flaw (CVSS 7.5) affecting evergreen. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Evergreen before 2.5.9, 2.6.x before 2.6.7, and 2.7.x before 2.7.4 allows remote attackers to bypass an intended access restriction and obtain sensitive information about org unit settings by leveraging failure of open-ils.actor.ou_setting.ancestor_default to enforce view_perm when no auth token is provided.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.1% (top 12%)
CISA exploited list	No
Weakness	CWE-200
Published	2018-02-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: evergreen-ils

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

Am I affected?

Timeline

2018-02-01 17:29 UTCPublished CVE record published
2026-06-17 00:23 UTCUpdated Record last modified

evergreen-ils evergreen UPGRADE

Affected: < 2.5.9 · >= 2.6.0 and < 2.6.7 · >= 2.7.0 and < 2.7.4

Fixed in: 2.5.9, 2.6.7, 2.7.4

Safe to downgrade to: a release before 2.6.0

1. Check installed version

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

2. UPGRADE to 2.5.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade evergreen

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade evergreen

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.6.0 (Debian / Ubuntu)

apt-cache madison evergreen sudo apt install evergreen=<VERSION_BEFORE_2.6.0> sudo apt-mark hold evergreen

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list evergreen sudo dnf downgrade evergreen-<VERSION_BEFORE_2.6.0> sudo dnf versionlock add evergreen

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.

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-2015-2204?

evergreen: upgrade to 2.5.9, 2.6.7, 2.7.4. Exact commands for each OS are on this page.

Is CVE-2015-2204 being exploited?

CVE-2015-2204 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-2015-2204 affect?

CVE-2015-2204 affects evergreen. Severity is high (CVSS 7.5). Evergreen before 2.5.9, 2.6.x before 2.6.7, and 2.7.x before 2.7.4 allows remote attackers to bypass an intended access restriction and obtain sensitive information about org unit settings by leveraging failure of open-ils.actor.ou_setting.

How urgent is CVE-2015-2204?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2015-2203 MEDIUM 6.5 DOWNGRADE Evergreen 2.5.9, 2.6.7, and 2.7.4 allows remote authenticated users with STAFF_LOGIN permission to obtain sens
CVE-2013-7435 MEDIUM 6.5 UPGRADE The open-ils.pcrud endpoint in Evergreen before 2.5.9, 2.6.x before 2.6.7, and 2.7.x before 2.7.4 allows remot

References

← Back to latest CVEs