Skip to content

Incorrect Provision of Specified Functionality in qutebrowser

Low severity GitHub Reviewed Published May 7, 2020 in qutebrowser/qutebrowser • Updated Oct 16, 2024

Package

pip qutebrowser (pip)

Affected versions

< 1.11.1

Patched versions

1.11.1

Description

Description

After a certificate error was overridden by the user, qutebrowser displays the URL as yellow (colors.statusbar.url.warn.fg). However, when the affected website was subsequently loaded again, the URL was mistakenly displayed as green (colors.statusbar.url.success_https). While the user already has seen a certificate error prompt at this point (or set content.ssl_strict to false which is not recommended), this could still provide a false sense of security.

Affected versions and patches

All versions of qutebrowser are believed to be affected, though versions before v0.11.x couldn't be tested.

The issue is fixed in qutebrowser v1.11.1 (pending release) and v1.12.0 (unreleased). Backported patches for older versions are available, but no further releases are planned.

Mitigation

If you are unable to upgrade:

  • Treat any host with a certificate exception as insecure, ignoring the URL color
  • Or set content.ssl_strict to True (instead of 'ask'), preventing certificate exceptions

References

References

@The-Compiler The-Compiler published to qutebrowser/qutebrowser May 7, 2020
Published by the National Vulnerability Database May 7, 2020
Reviewed May 8, 2020
Published to the GitHub Advisory Database May 8, 2020
Last updated Oct 16, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(70th percentile)

Weaknesses

Incorrect Provision of Specified Functionality

The code does not function according to its published specifications, potentially leading to incorrect usage. Learn more on MITRE.

CVE ID

CVE-2020-11054

GHSA ID

GHSA-4rcq-jv2f-898j

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.