"Recently, the Qt Project's security team was made aware of an issue regarding QProcess and determined it to be a security issue on Unix-based platforms only. We do not believe this to be a considerable risk for applications as the likelihood of it being triggered is minimal.
Specifically, the problem is around using QProcess to start an application without having an absolute path, and as a result, it depends on it finding it in the PATH environment variable. As a result, it may be possible for an attacker to place their copy of the executable in question inside the working/current directory for the QProcess and have it invoked that instead.
This situation is expected on Windows because it will search that directory first before the PATH environment variable finds the executable in question. However, it is not normal on Unix-based platforms to search the working/current directory if it cannot find it in the PATH environment variable. Therefore, it could enable an attacker to place a malicious executable there with the same name.
If you are using QProcess with an absolute or relative path, then this is not a problem; it will invoke that one specifically, but if you are using it like:
it could run into this problem."
KDE are currently waiting for upstream if they will fix the tests broken by this change.
The bug has been referenced in the following commit(s):
Author: Ionen Wolkens <firstname.lastname@example.org>
AuthorDate: 2022-04-01 17:20:45 +0000
Commit: Ionen Wolkens <email@example.com>
CommitDate: 2022-04-01 17:46:36 +0000
www-client/qutebrowser: add 2.5.0
This includes a workaround for CVE-2022-25255 wrt bug #833583
Signed-off-by: Ionen Wolkens <firstname.lastname@example.org>
www-client/qutebrowser/Manifest | 1 +
www-client/qutebrowser/qutebrowser-2.5.0.ebuild | 122 ++++++++++++++++++++++++
2 files changed, 123 insertions(+)
Cleanup done in commit 2e7a463a4c38e186585f1721fe20e99b304a3f95 then.