Vulnerability in drupal7 (UBUNTU-CVE-2021-32610)

Summary

vulnerability in drupal7 (UBUNTU-CVE-2021-32610). Confidential information can be exposed externally. Mitigation: upgrade to `1:1.10.1+submodules+notgz-6ubuntu0.3+esm1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **UBUNTU-CVE-2021-32610** has been found in drupal7. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade drupal7 to **1:1.10.1+submodules+notgz-6ubuntu0.3+esm1** or later. If unsure, ask your IT team or search "drupal7 UBUNTU-CVE-2021-32610" on the vendor's site.

UBUNTU-CVE-2021-32610 (drupal7) — Attack vector: local / no user interaction Patched: `1:1.10.1+submodules+notgz-6ubuntu0.3+esm1` — 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 drupal7.

📍 Affected scope

drupal7 — .

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **1:1.10.1+submodules+notgz-6ubuntu0.3+esm1**.

🛡️ 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 'drupal7' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

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

Affected packages

Ubuntu:Pro:14.04:LTS drupal7

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:16.04:LTS drupal7

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:16.04:LTS php-pear

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.10.1+submodules+notgz-6ubuntu0.3+esm1"}]}]

Ubuntu:18.04:LTS php-pear

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.10.5+submodules+notgz-1ubuntu1.18.04.4"}]}]

Ubuntu:20.04:LTS php-pear

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.10.9+submodules+notgz-1ubuntu0.20.04.3"}]}]

Ubuntu:22.04:LTS php-pear

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:1.10.12+submodules+notgz+20210212-1ubuntu1"}]}]

References

advisory https://ubuntu.com/security/notices/USN-5027-1
advisory https://ubuntu.com/security/notices/USN-5027-2
report https://ubuntu.com/security/CVE-2021-32610
report https://www.drupal.org/sa-core-2021-004
report https://pear.php.net/package/Archive_Tar/download/1.4.14/
report https://www.cve.org/CVERecord?id=CVE-2021-32610