831220 – (CVE-2021-46168) <sci-mathematics/spin-6.5.2-r1: OOB write

Bug 831220 (CVE-2021-46168) - <sci-mathematics/spin-6.5.2-r1: OOB write

Summary: <sci-mathematics/spin-6.5.2-r1: OOB write

Status:	RESOLVED FIXED

Alias:	CVE-2021-46168

Product:	Gentoo Security
Classification:	Unclassified
Component:	Vulnerabilities (show other bugs)
Hardware:	All Linux

Importance:	Normal trivial (vote)
Assignee:	Gentoo Security

URL:	https://github.com/nimble-code/Spin/i...
Whiteboard:	~3 [noglsa]
Keywords:

Depends on:
Blocks:

Reported:	2022-01-15 08:17 UTC by John Helmert III
Modified:	2022-01-17 05:42 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

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

Note You need to log in before you can comment on or make changes to this bug.

Description John Helmert III archtester

2022-01-15 08:17:53 UTC

CVE-2021-46168:

Spin v6.5.1 was discovered to contain an out-of-bounds write in lex() at spinlex.c.

Comment 1 Larry the Git Cow gentoo-dev

2022-01-16 08:57:25 UTC

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=69c2ae786d9151a8358198a73a8bcd0583ac9a1f

commit 69c2ae786d9151a8358198a73a8bcd0583ac9a1f
Author:     Marek Szuba <marecki@gentoo.org>
AuthorDate: 2022-01-16 08:56:16 +0000
Commit:     Marek Szuba <marecki@gentoo.org>
CommitDate: 2022-01-16 08:57:12 +0000

    sci-mathematics/spin: backport upstream fix for CVE-2021-46168
    
    Closes: https://bugs.gentoo.org/831220
    Signed-off-by: Marek Szuba <marecki@gentoo.org>

 .../spin/files/spin-6.5.2-nesting_limit.patch      | 55 ++++++++++++++++++++++
 .../{spin-6.5.2.ebuild => spin-6.5.2-r1.ebuild}    |  3 +-
 2 files changed, 57 insertions(+), 1 deletion(-)

Comment 2 Marek Szuba (RETIRED) archtester

2022-01-16 08:57:59 UTC

No vulnerable versions left in the tree.

Comment 3 John Helmert III archtester

2022-01-16 19:35:35 UTC

All done, thanks!

Comment 4 Sam James archtester

2022-01-17 05:42:50 UTC

(In reply to Marek Szuba from comment #2)
> No vulnerable versions left in the tree.

(but please don't close security bugs yourself to ensure procedure is followed (metadata updated, no other action required from us, etc))