Bug 1194276 (CVE-2021-45948) - VUL-1: CVE-2021-45948: assimp: heap-based buffer overflow in _m3d_safestr
Summary: VUL-1: CVE-2021-45948: assimp: heap-based buffer overflow in _m3d_safestr
Status: RESOLVED FIXED
Alias: CVE-2021-45948
Product: openSUSE Distribution
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Leap 15.3
Hardware: Other Other
: P4 - Low : Minor (vote)
Target Milestone: ---
Assignee: Christophe Marin
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/319357/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-04 07:14 UTC by Alexander Bergmann
Modified: 2022-01-04 12:22 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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 Alexander Bergmann 2022-01-04 07:14:11 UTC 
CVE-2021-45948

Open Asset Import Library (aka assimp) 5.1.0 and 5.1.1 has a heap-based buffer
overflow in _m3d_safestr (called from m3d_load and
Assimp::M3DWrapper::M3DWrapper).

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45948
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34416
https://github.com/google/oss-fuzz-vulns/blob/main/vulns/assimp/OSV-2021-775.yaml
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45948
http://www.cvedetails.com/cve/CVE-2021-45948/
Comment 1 Alexander Bergmann 2022-01-04 07:16:56 UTC 
From what I see in our code streams we are not affected. Please double check.

openSUSE:Factory               5.1.4
openSUSE:Leap:15.2             3.3.1
openSUSE:Backports:SLE-15-SP3  3.3.1
openSUSE:Backports:SLE-15-SP4  5.1.3
Comment 2 Christophe Marin 2022-01-04 09:06:56 UTC 
I have a doubt about the affected versions.

This is fixed in our package by https://github.com/assimp/assimp/commit/30f17aa20

/data/misc/assimp (master) # git tag --contains 30f17aa20
v5.1.0
v5.1.1
v5.1.2
v5.1.3
v5.1.4
v5.1.5

Version 3.3.1 is not affected.
Comment 3 Christophe Marin 2022-01-04 12:22:43 UTC 
Closing. None of our packages are affected.