- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202401-21
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: KTextEditor: Arbitrary Local Code Execution
     Date: January 15, 2024
     Bugs: #832447
       ID: 202401-21

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

A vulnerability has been found in KTextEditor where local code can be
executed without user interaction.

Background
==========

Framework providing a full text editor component for KDE.

Affected packages
=================

Package                     Vulnerable    Unaffected
--------------------------  ------------  ------------
kde-frameworks/ktexteditor  < 5.90.0-r2   >= 5.90.0-r2

Description
===========

A vulnerability has been discovered in KTextEditor. Please review the
CVE identifiers referenced below for details.

Impact
======

KTextEditor executes binaries without user interaction in a few cases,
e.g. KTextEditor will try to check on external file modification via
invoking the "git" binary if the file is known in the repository with
the new content.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All KTextEditor users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=kde-frameworks/ktexteditor-5.90.0-r2"

References
==========

[ 1 ] CVE-2022-23853
      https://nvd.nist.gov/vuln/detail/CVE-2022-23853

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202401-21

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2024 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-202401-21: KTextEditor: Arbitrary Local Code Execution

A vulnerability has been found in KTextEditor where local code can be executed without user interaction.

Summary

A vulnerability has been discovered in KTextEditor. Please review the CVE identifiers referenced below for details.

Resolution

All KTextEditor users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=kde-frameworks/ktexteditor-5.90.0-r2"

References

[ 1 ] CVE-2022-23853 https://nvd.nist.gov/vuln/detail/CVE-2022-23853

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202401-21

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Normal
Title: KTextEditor: Arbitrary Local Code Execution
Date: January 15, 2024
Bugs: #832447
ID: 202401-21

Synopsis

A vulnerability has been found in KTextEditor where local code can be executed without user interaction.

Background

Framework providing a full text editor component for KDE.

Affected Packages

Package Vulnerable Unaffected -------------------------- ------------ ------------ kde-frameworks/ktexteditor < 5.90.0-r2 >= 5.90.0-r2

Impact

KTextEditor executes binaries without user interaction in a few cases, e.g. KTextEditor will try to check on external file modification via invoking the "git" binary if the file is known in the repository with the new content.

Workaround

There is no known workaround at this time.

Related News