Vulnerability in Webmin (CVE-2018-8712)

Summary

Vulnerability in Webmin (CVE-2018-8712). Successful exploitation can lead to full system takeover. Exploitable via GET /syslog/save_log.cgi.

Original description

The description as published by the source.

An issue was discovered in Webmin 1.840 and 1.880 when the default Yes setting of "Can view any file as a log file" is enabled. As a result of weak default configuration settings, limited users have full access rights to the underlying Unix system files, allowing the user to read sensitive data from the local system (using Local File Include) such as the '/etc/shadow' file via a "GET /syslog/save_log.cgi?view=1&file=/etc/shadow" request.

Source: OSV.dev (Open Source Vulnerabilities) NVD 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-8712 has been found in Webmin.
Attackers can target a specific entry point like GET /syslog/save_log.cgi over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Webmin CVE-2018-8712" on the vendor's site.

CVE-2018-8712 (Webmin)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /syslog/save_log.cgi
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 Webmin. Attackers reach the vulnerable code path via GET /syslog/save_log.cgi without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Webmin. Attack surface: GET /syslog/save_log.cgi.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 GET /syslog/save_log.cgi requests with malformed payloads or SQL meta-characters. Run grep -r 'Webmin' . 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 'Webmin' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Webmin を grep し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'GET /syslog/save_log.cgi' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで GET /syslog/save_log.cgi への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Post-deployment verification verify
```
Replay attack against GET /syslog/save_log.cgi on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

report 7elements.co.uk