Vulnerability in Anymail django-anymail (CVE-2018-1000089)

Summary

Vulnerability in Anymail django-anymail (CVE-2018-1000089). Confidential information can be exposed externally. Mitigation: upgrade to 1.4 or later.

Original description

The description as published by the source.

Anymail django-anymail version version 0.2 through 1.3 contains a CWE-532, CWE-209 vulnerability in WEBHOOK_AUTHORIZATION setting value that can result in An attacker with access to error logs could fabricate email tracking events. This attack appear to be exploitable via If you have exposed your Django error reports, an attacker could discover your ANYMAIL_WEBHOOK setting and use this to post fabricated or malicious Anymail tracking/inbound events to your app. This vulnerability appears to have been fixed in v1.4.

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-1000089 has been found in Anymail django-anymail.
Confidential information can be exposed externally.
What to do: upgrade Anymail django-anymail to 1.4 or later.
If unsure, ask your IT team or search "Anymail django-anymail CVE-2018-1000089" on the vendor's site.

CVE-2018-1000089 (Anymail django-anymail)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.4 — 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 Anymail django-anymail.

📍 Affected scope

Check the vendor advisory for the affected versions of Anymail django-anymail.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 1.4.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Anymail django-anymail を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Anymail django-anymail to 1.4
```
ステージング環境で 1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2018-1000089 django-anymail Fixed in: 1.4-1

References

advisory github.com
patch github.com