Vulnerability in feedgen (CVE-2020-5227)
Summary
Vulnerability in feedgen (CVE-2020-5227). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.9.0 or later.
Original description
The description as published by the source.
Impact
The feedgen library allows supplying XML as content for some of the available fields. This XML will be parsed and integrated into the existing XML tree. During this process, feedgen is vulnerable to XML Denial of Service Attacks (e.g. XML Bomb).
This becomes a concern in particular if feedgen is used to include content from untrused sources and if XML (including XHTML) is directly included instead of providing plain tex content only.
Patches
This problem has been fixed in feedgen 0.9.0 which disallows XML entity expansion and external resources.
Workarounds
Updating is strongly recommended and should not be problematic. Nevertheless, as a workaround, avoid providing XML directly to feedgen or ensure that no entity expansion is part of the XML.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in lkiesow/python-feedgen
- Send an email to security@lkiesow.de
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-2020-5227 has been found in feedgen.
Risk of unauthorized operations or information disclosure.
What to do: upgrade feedgen to 0.9.0 or later.
If unsure, ask your IT team or search "feedgen CVE-2020-5227" on the vendor's site.
CVE-2020-5227 (feedgen) — CWE-776
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.9.0 — apply immediately
Workaround: Updating is strongly recommended and should not be problematic.
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.
A vulnerability (CWE-776) exists in feedgen.
Check the vendor advisory for the affected versions of feedgen.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.9.0.
Workaround: Updating is strongly recommended and should not be problematic.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'feedgen' . 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
-
1Identify exposure identify
grep -r 'feedgen' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
feedgenを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Updating is strongly recommended and should not be problematic.パッチが適用されるまでの応急処置として、Updating is strongly recommended and should not be problematic. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade feedgen to 0.9.0ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web docs.microsoft.com
- web github.com
- web lists.fedoraproject.org