Drupal has shipped fixed releases across all of its supported branches to close a critical flaw in Drupal core that could let an attacker with no login credentials attempt to reinstall a site through the built-in installer, with the potential for full site takeover or remote code execution.
The Drupal Security Team disclosed the issue after determining that, under specific conditions, an unauthenticated attacker can reach the installer and drive a reinstall of an existing site. Drupal rates the vulnerable configurations as uncommon — a caveat that tempers the critical severity rating, but one that should not be read as "never": uncommon setups still exist in the wild, and attackers routinely scan for them at scale.
The fixes shipped on 18 November, with the disclosure reported on 19 November by The Hacker News. The project did not publish a CVE identifier or a branch-by-branch affected-version list in the material summarised here, so site administrators should consult Drupal's own security advisory directly for the version-by-version fix list before planning upgrades.
Why the installer matters
The durable lesson from this advisory goes beyond patching a single bug. Drupal's installer is one-time setup tooling: it is meant to be reachable only while a site is being built, then locked away once configuration completes. When that path stays exposed on a running installation, it becomes a standing, unauthenticated attack surface — no credentials, no valid session, and no exploitation chain required beyond reaching the right URL.
That framing shifts the response from "apply the update" to configuration hygiene as well. Patching closes this specific hole, but it does not answer the broader question of whether other transient setup artefacts are still reachable on a production host. A common sign of installer exposure is a reachable install.php path (or its equivalent front-controller route) on a site that is clearly already configured and serving content — though that is our own diagnostic read rather than a confirmed entry point named in this advisory, and administrators should verify against Drupal's guidance rather than treat it as a given.
Interim mitigation
Drupal's guidance points administrators toward restricting installer access at the HTTP layer — blocking the installer path at the web server or reverse proxy — as an interim measure for sites that cannot apply the fixed releases immediately. Organisations that maintain a standard hardening baseline may already enforce this; those that do not should treat it as a stopgap, not a substitute for upgrading.
Broadly speaking, the story is relevant to Hong Kong IT professionals managing self-hosted Drupal installations — not because of any local advisory, but because the same scanning techniques used against installations worldwide apply here too. Sites that were set up by a vendor years ago and rarely revisited are exactly the ones most likely to still expose setup paths.
Action list
- Identify every Drupal installation in the estate, including staging and forgotten marketing sites.
- Check each one's installer path for reachability, not just its core version.
- Apply the fixed releases for the relevant supported branch, using Drupal's security advisory for the definitive version list.
- Where an upgrade cannot happen immediately, restrict installer access at the HTTP layer as an interim control.
- Re-audit after patching for other setup-time artefacts left reachable in production.
The full advisory is available through Drupal's official security announcements.
Drupal 已在所有受支援的分支發布修正版本,修補核心中的一項嚴重漏洞。該漏洞可讓攻擊者在無需登入憑證的情況下,透過內建安裝程式嘗試重新安裝網站,從而有機會完全接管網站或執行遠端代碼。
Drupal 安全團隊在確認相關情況後披露了此問題:在特定條件下,未經認證的攻擊者可以進入安裝程式,並驅動對現有網站的重新安裝。Drupal 評估受影響的配置屬罕見——這一前提使「嚴重」級別的評級有所緩和,但不應被理解為「絕不可能出現」:罕見的配置在現實環境中依然存在,而攻擊者向來會大規模掃描這類目標。
修訂版本於 11 月 18 日發布,相關披露則由 The Hacker News 於 11 月 19 日報道。此項目在本文所總結的資料中並未公布 CVE 編號或按分支列出的受影響版本清單,因此網站管理員在規劃升級前,應直接查閱 Drupal 官方的安全公告,以獲取逐版本的修補清單。
為何安裝程式值得關注
這份公告帶來的啟示不止於修補單一漏洞。Drupal 的安裝程式屬一次性設定工具:它只應在網站建立期間可被存取,設定完成後便須封閉。當該路徑在運行中的安裝環境仍然暴露時,便會成為一個長期存在的未經認證攻擊面——無需憑證、無需有效 session,除了存取正確的 URL 之外,亦不需任何漏洞利用鏈。
這一角度意味著應對措施不單是「套用更新」,還包括配置衛生。補丁封堵了這個特定漏洞,但並未回答一個更廣泛的問題:其他臨時性設定產物是否在生產主機上仍可存取。安裝程式暴露的常見跡象,是在一個明顯已完成設定並正在提供內容的網站上,install.php 路徑(或其等效的 front-controller 路由)仍可存取——不過這屬於我們自身的判讀,並非本公告所確認的入侵點,管理員應按 Drupal 的指引加以核實,而非視之為既定事實。
臨時緩解措施
Drupal 的指引建議管理員在 HTTP 層面限制安裝程式的存取——在 web server 或反向代理(reverse proxy)層面封鎖安裝程式路徑——作為無法立即套用修正版本的網站的臨時措施。已訂立標準加固基線的機構可能已實施相關限制;未有此舉的機構則應將其視為權宜之計,而非升級的替代方案。
總括而言,這則事件與香港管理自架 Drupal 安裝環境的 IT 專業人員息息相關——原因並非本地有相關公告,而是針對全球各地安裝環境使用的同一套掃描技術,同樣適用於此處。多年前由供應商搭建、其後甚少重新檢視的網站,正是最有可能仍然暴露設定路徑的目標。
行動清單
- 識別環境內所有 Drupal 安裝,包括 staging 環境及遭遺忘的市場推廣網站。
- 檢查各個安裝的安裝程式路徑是否可存取,而不只是其 core 版本。
- 按相關受支援分支套用修正版本,並以 Drupal 安全公告作為權威版本清單。
- 如無法立即升級,須在 HTTP 層面限制安裝程式的存取,作為臨時控制措施。
- 完成補丁後重新審計,檢查生產環境中是否仍有其他設定階段產物可供存取。
完整公告可於 Drupal 官方安全通告查閱。
