Bug 33348 - espeak-ng new security issues CVE-2023-4999[0-4]
Summary: espeak-ng new security issues CVE-2023-4999[0-4]
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL:
Whiteboard: MGA9-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2024-07-01 15:28 CEST by Nicolas Salguero
Modified: 2024-07-02 18:24 CEST (History)
2 users (show)

See Also:
Source RPM: espeak-ng-1.51.1-2.mga10.src.rpm
CVE: CVE-2023-49990, CVE-2023-49991, CVE-2023-49992, CVE-2023-49993, CVE-2023-49994
Status comment: Patches available from Ubuntu

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nicolas Salguero 2024-07-01 15:28:23 CEST 
Ubuntu has issued an advisory on July 1:
https://ubuntu.com/security/notices/USN-6858-1

Mageia 9 is also affected.
Nicolas Salguero 2024-07-01 15:29:20 CEST

Source RPM: (none) => espeak-ng-1.51.1-2.mga10.src.rpm
Whiteboard: (none) => MGA9TOO
Status comment: (none) => Patches available from Ubuntu
CVE: (none) => CVE-2023-49990, CVE-2023-49991, CVE-2023-49992, CVE-2023-49993, CVE-2023-49994

Nicolas Salguero 2024-07-01 16:08:29 CEST

Assignee: bugsquad => geiger.david68210

Comment 1 David GEIGER 2024-07-01 17:02:51 CEST 
Done for both mga9 and Cauldron!

Whiteboard: MGA9TOO => (none)
Version: Cauldron => 9

Comment 2 David GEIGER 2024-07-01 17:04:26 CEST 
Assigning to QA,

Packages in 9/Core/Updates_testing:
======================
espeak-ng-1.51.1-1.1.mga9
espeak-ng-vim-1.51.1-1.1.mga9.noarch.rpm
libespeak-ng-devel-1.51.1-1.1.mga9
libespeak-ng1-1.51.1-1.1.mga9
lib64espeak-ng-devel-1.51.1-1.1.mga9
lib64espeak-ng1-1.51.1-1.1.mga9

From SRPMS:
espeak-ng-1.51.1-1.1.mga9.src.rpm

Assignee: geiger.david68210 => qa-bugs

Comment 3 katnatek 2024-07-02 02:17:15 CEST 
RH mageia 9 x86_64

LC_ALL=C urpmi --auto --auto-update
medium "QA Testing (32-bit)" is up-to-date
medium "QA Testing (64-bit)" is up-to-date
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date

installing espeak-ng-1.51.1-1.1.mga9.x86_64.rpm lib64espeak-ng1-1.51.1-1.1.mga9.x86_64.rpm from //home/katnatek/qa-testing/x86_64
Preparing...                     ##################################################################################################
      1/2: lib64espeak-ng1       ##################################################################################################
      2/2: espeak-ng             ##################################################################################################
      1/2: removing espeak-ng-1.51.1-1.mga9.x86_64
                                 ##################################################################################################
      2/2: removing lib64espeak-ng1-1.51.1-1.mga9.x86_64
                                 ##################################################################################################

espeak-ng "This is a test"
I can hear "This is a test"

Whiteboard: (none) => MGA9-64-OK
CC: (none) => andrewsfarm

katnatek 2024-07-02 02:21:51 CEST

Keywords: (none) => advisory

Comment 4 Thomas Andrews 2024-07-02 13:15:30 CEST 
Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 5 Mageia Robot 2024-07-02 18:24:09 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2024-0249.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.