CVE-2017-2239: Marp versions v0.0.10 and earlier may allow an attacker to access local resources and files using JavaScript.

Routine

MEDIUM 5.3DOWNGRADE

CVE-2017-2239 is a medium-severity flaw (CVSS 5.3) affecting marp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Marp versions v0.0.10 and earlier may allow an attacker to access local resources and files using JavaScript.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-200
Published	2017-07-07
Last modified	2026-06-17

Publisher (CNA): JPCERT/CC · Vendor: marp

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

Am I affected?

Timeline

2017-07-07 13:29 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

marp marp DOWNGRADE

Affected: 0.0.10

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.0.10

1. Check installed version

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

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

apt-cache madison marp sudo apt install marp=<VERSION_BEFORE_0.0.10> sudo apt-mark hold marp

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

dnf --showduplicates list marp sudo dnf downgrade marp-<VERSION_BEFORE_0.0.10> sudo dnf versionlock add marp

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-2017-2239?

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

Is CVE-2017-2239 being exploited?

CVE-2017-2239 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-2239 affect?

CVE-2017-2239 affects marp. Severity is medium (CVSS 5.3). Marp versions v0.0.10 and earlier may allow an attacker to access local resources and files using JavaScript.

How urgent is CVE-2017-2239?

Priority 30/100. No elevated risk signals yet.

References

← Back to latest CVEs