Vulnerability in Parsedown (CVE-2018-1000162)

Summary

Vulnerability in Parsedown (CVE-2018-1000162). Risk of unauthorized operations or information disclosure. Exploitable via setMarkupEscaped. Mitigation: upgrade to 1.7.0 or later.

Original description

The description as published by the source.

Parsedown version prior to 1.7.0 contains a Cross Site Scripting (XSS) vulnerability in setMarkupEscaped for escaping HTML that can result in JavaScript code execution. This attack appears to be exploitable via specially crafted markdown that allows it to side step HTML escaping by breaking AST boundaries. This vulnerability appears to have been fixed in 1.7.0 and later.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2018-1000162 has been found in Parsedown.
Attackers can target a specific entry point like setMarkupEscaped over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Parsedown to 1.7.0 or later.
If unsure, ask your IT team or search "Parsedown CVE-2018-1000162" on the vendor's site.

CVE-2018-1000162 (Parsedown)
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: setMarkupEscaped
Patched: 1.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Parsedown. Attackers reach the vulnerable code path via setMarkupEscaped without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Parsedown. Attack surface: setMarkupEscaped.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Parsedown' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'Parsedown' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Parsedown を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Parsedown to 1.7.0
```
ステージング環境で 1.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

advisory github.com
advisory github.com