CVE-2015-5070: The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_b

Q: How do I fix CVE-2015-5070?

battle for wesnoth: upgrade to newer than 1.12.2; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2015-5070 being exploited?

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

Q: What does CVE-2015-5070 affect?

CVE-2015-5070 affects battle for wesnoth, fedora. Severity is low (CVSS 3.1). The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.4 and 1.13.x before 1.13.1, when a case-insensitive filesystem is used, allow remote at

Q: How urgent is CVE-2015-5070?

Priority 29/100. No elevated risk signals yet.

Routine

LOW 3.1UPGRADEMITIGATE

CVE-2015-5070 is a low-severity flaw (CVSS 3.1) affecting battle for wesnoth, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.4 and 1.13.x before 1.13.1, when a case-insensitive filesystem is used, allow remote attackers to obtain sensitive information via vectors related to inclusion of .pbl files from WML. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-5069.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.1 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Weakness	CWE-200
Published	2017-09-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: fedoraproject · wesnoth

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

Am I affected?

Timeline

2017-09-26 14:29 UTCPublished CVE record published
2026-06-17 00:28 UTCUpdated Record last modified

wesnoth battle for wesnoth UPGRADE

Affected: <= 1.12.2 · 1.13.0

Fixed in: newer than 1.12.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy battle-for-wesnoth || rpm -q battle-for-wesnoth || battle-for-wesnoth --version

2. UPGRADE to newer than 1.12.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade battle-for-wesnoth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade battle-for-wesnoth

Note

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

fedoraproject fedora MITIGATE

Affected: 21 · 22

Fixed in: no fixed release known

Safe to downgrade to: a release before 21

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-5070?

battle for wesnoth: upgrade to newer than 1.12.2; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2015-5070 being exploited?

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

CVE-2015-5070 affects battle for wesnoth, fedora. Severity is low (CVSS 3.1). The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.4 and 1.13.x before 1.13.1, when a case-insensitive filesystem is used, allow remote at

How urgent is CVE-2015-5070?

Priority 29/100. No elevated risk signals yet.

Related CVEs

CVE-2015-5069 MEDIUM 4.3 UPGRADE MITIGATE The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_b

References

← Back to latest CVEs