Vulnerability in qutebrowser (CVE-2018-1000559)

Summary

Vulnerability in qutebrowser (CVE-2018-1000559). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.3.3 or later.

Original description

The description as published by the source.

qutebrowser version introduced in v0.11.0 (1179ee7a937fb31414d77d9970bac21095358449) contains a Cross Site Scripting (XSS) vulnerability in history command, qute://history page that can result in Via injected JavaScript code, a website can steal the user's browsing history. This attack appear to be exploitable via the victim must open a page with a specially crafted attribute, and then open the qute://history site via the :history command. This vulnerability appears to have been fixed in fixed in v1.3.3 (4c9360237f186681b1e3f2a0f30c45161cf405c7, to be released today) and v1.4.0 (5a7869f2feaa346853d2a85413d6527c87ef0d9f, released later this week).

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-1000559 has been found in qutebrowser.
Risk of unauthorized operations or information disclosure.
What to do: upgrade qutebrowser to 1.3.3 or later.
If unsure, ask your IT team or search "qutebrowser CVE-2018-1000559" on the vendor's site.

CVE-2018-1000559 (qutebrowser)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.3.3 — 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 qutebrowser.

📍 Affected scope

Check the vendor advisory for the affected versions of qutebrowser.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.3.3.

🛡️ 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 'qutebrowser' . 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 'qutebrowser' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で qutebrowser を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade qutebrowser to 1.3.3
```
ステージング環境で 1.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
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-1000559 qutebrowser Fixed in: 1.3.3-1

References

patch github.com
patch github.com
report github.com