Change History (5)
comment:1 by , 5 years ago
Priority: | normal → high |
---|
comment:2 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Builds ok with existing instructions.
comment:3 by , 5 years ago
NB I wasn't using the wayland patch, that has almost all been applied in this version.
comment:5 by , 5 years ago
Some additional information on the QLibrary vulnerability:
Issue 2) CVE-2020-0570 Score: 7.3 (High) - CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C * Vendor: Qt Project * Product: Qt * Versions affected: 5.12.0 through 5.14.0 * Versions fixed: 5.14.1 (released), 5.12.7, 5.9.10 (future) * Issue: local attack, loading and execution of untrusted code * Scope: class QLibrary (qtbase/src/corelib/plugin) * Reference: https://bugreports.qt.io/browse/QTBUG-81272 * Description: QLibrary in Qt versions 5.12.0 through 5.14.0, on certain x86 machines, would search for certain libraries and plugins relative to current working directory of the application, which allows an attacker that can place files in the file system and influence the working directory of Qt-based applications to load and execute malicious code. This issue was verified on Linux and probably affects all Unix operating systems, other than macOS (Darwin). This issue does not affect Windows.
Note:
See TracTickets
for help on using tickets.
It looks like this contains some security fixes:
For the QtWebEngine ones: