| Summary: | xterm new security issue CVE-2022-24130 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, davidwhodgins, nicolas.salguero, sysadmin-bugs |
| Version: | 8 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA8-64-OK | ||
| Source RPM: | xterm-363-1.1.mga8.src.rpm | CVE: | CVE-2022-24130 |
| Status comment: | |||
|
Description
David Walser
2022-01-31 14:40:51 CET
David Walser
2022-01-31 14:40:59 CET
Whiteboard:
(none) =>
MGA8TOO No consistent committer for this pkg, so have to assign the bug globally. Assignee:
bugsquad =>
pkg-bugs Suggested advisory: ======================== The updated package fixes a security vulnerability: xterm through Patch 370, when Sixel support is enabled, allows attackers to trigger a buffer overflow in set_sixel in graphics_sixel.c via crafted text. (CVE-2022-24130) References: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24130 https://www.openwall.com/lists/oss-security/2022/01/31/1 ======================== Updated package in core/updates_testing: ======================== xterm-363-1.2.mga8 from SRPM: xterm-363-1.2.mga8.src.rpm CC:
(none) =>
nicolas.salguero Tested in a VirtualBox Plasma guest. Installed xterm and a dependency, no installation issues. Ran xterm, tried a few commands - launched Firefox and vlc, launched MCC (which asked for the root password). Switched to root, ran systemctl status, then journalctl -ab, then tried MCC again. No issues at all. This looks good. Validating. Advisory in Comment 2. Keywords:
(none) =>
validated_update
Dave Hodgins
2022-02-05 19:36:15 CET
Keywords:
(none) =>
advisory An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2022-0051.html Status:
ASSIGNED =>
RESOLVED Debian-LTS has issued an advisory for this on February 7: https://www.debian.org/lts/security/2022/dla-2913 |