[Debian-med-packaging] Bug#1154239: trixie-pu: package invesalius/3.1.99998-7+deb13u1
valentintorassacolombero at gmail.com
valentintorassacolombero at gmail.com
Tue Nov 17 14:11:51 GMT 2026
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: invesalius at packages.debian.org
Control: affects -1 + src:invesalius
User: release.debian.org at packages.debian.org
Usertags: pu
[ Reason ]
invesalius 3.1.99998-7 in trixie is affected by two CVEs and by a grave
bug, all fixed in unstable:
- CVE-2024-44825 (#1136204), path traversal when opening an .inv3
project. Fixed in 3.1.99998-9.
- CVE-2024-42845 (#1082875), eval() of DICOM tag values. Fixed in
3.1.99998-8.
- #1153854 (grave), the GUI does not start because the package does not
depend on python3-six. #1147757 reports the same missing dependency.
Fixed in 3.1.99998-9.
The security tracker marks both CVEs <no-dsa> (minor issue) for trixie.
This update fixes all three in a point release, with the same changes as
unstable.
[ Impact ]
- An .inv3 project is a tar file. 3.1.99998-7 writes every member to
os.path.join(<temporary folder>, <member name>) without checking the
name. A crafted project with "..", an absolute member name, or an
absolute first directory creates or overwrites files anywhere the user
can write, as soon as the user opens it (also with --no-gui).
- The DICOM reader passes the Image Position (Patient) and Slice Location
values to eval(). A crafted DICOM file can run Python code as the user.
- 11_add_auibar.patch makes invesalius/gui/widgets/auibar.py import six,
but python3-six is not in Depends. On a system that does not have it
installed, "invesalius3" fails at startup with "ModuleNotFoundError:
No module named 'six'" and no window opens. "invesalius3 --no-gui"
does not load that module, so the autopkgtest does not catch it.
[ Tests ]
All on amd64, in fresh debian:trixie containers (Python 3.13.5),
on 2026-11-16 and again on 2026-11-17 after adding the dependency:
- Full build (arch any and all) with dpkg-buildpackage -us -uc. All 11
patches apply without fuzz or offset.
- autopkgtest (run-unit-test, superficial) passes with the null runner,
as a normal user.
- lintian: no errors. The same 3 warnings as 3.1.99998-7
(old-fsf-address-in-copyright-file). One new informational tag,
out-of-date-standards-version, from the new changelog date.
- I installed 3.1.99998-7 from the archive and this update in two
separate clean containers and ran the same checks on both:
* Four crafted .inv3 files: a ".." member, an absolute member name, an
absolute symlink followed by a file written through it, and an
absolute first directory. Opened with "invesalius3 --no-gui <file>",
3.1.99998-7 wrote 3 entries outside of the temporary folder (the
symlink one fails with a KeyError before writing). The update wrote
none: ".." and the symlink are rejected by tarfile, and absolute
names end up inside the temporary folder. The application then
reports an error because these are not real projects.
* The same files through invesalius.project.Extract() directly, plus
the DICOM checks below: 12 of 12 checks pass with the update, 7 fail
with 3.1.99998-7.
* Upstream's regression tests for the fix (tests/test_project_extract.py
from 61e92e0, run with pytest against the installed module): 5 passed
with the update; 4 failed and 1 passed with 3.1.99998-7.
* The Cranium sample from invesalius-examples (tar.gz) and a plain tar
copy of it give the same 11 files with the same content with both
versions. "invesalius3 --no-gui Cranium.inv3 --export-project x.hdf5"
works with both, and all datasets in the two HDF5 files are equal
except the export date.
* DICOM reader: with 3.1.99998-7, GetImageLocation() ran a crafted
value (it created a marker file). With the update, GetImagePosition()
and GetImageLocation() raise ValueError and run nothing. Normal
values still parse (position [-125.5, -120.0, 60.25], location 42.5).
- Missing dependency: I installed 3.1.99998-7 from the archive and this
update, without recommends, in two more clean containers, and started
"invesalius3" under Xvfb (language preset to English).
* 3.1.99998-7: python3-six is not installed. The start fails with the
same tracebacks as in #1153854 (ModuleNotFoundError for six, then
AttributeError in Startup2 and OnClose) and no window opens.
* The update pulls in python3-six 1.17.0-1. The "InVesalius 3" main
window opens and there is no traceback.
[ Risks ]
Low. All changes are the ones in unstable, applied unchanged:
fix-cve-2024-42845.patch since 3.1.99998-8 (May 2026),
fix-cve-2024-44825.patch and the python3-six dependency since
3.1.99998-9 (November 2026).
- Projects are now extracted with tarfile's "data" filter (PEP 706,
available in trixie's Python 3.13). Projects saved by InVesalius only
contain regular files under one relative directory, so they open as
before. Only a project with a member that the filter rejects (for
example "..", links that point outside, device files) now fails to
open, with an error. The unused Extract_() is removed; nothing calls
it.
- The DICOM change replaces eval() with float() for two tags only. Valid
decimal values give the same numbers; integer values now come back as
floats (-120.0 instead of -120), as in unstable and upstream.
- The new dependency is python3-six 1.17.0-1 from trixie, one small
Architecture: all package. It only adds that package where it is not
already installed.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
* fix-cve-2024-44825.patch (backport of upstream 61e92e0, from
unstable 3.1.99998-9): Extract() in invesalius/project.py passes
every member through tarfile.data_filter() and extracts it with
filter="data". The returned file list uses the filtered names.
A member that the filter rejects stops the extraction. The unused
Extract_() is removed.
* fix-cve-2024-42845.patch (upstream 020cd60, from unstable
3.1.99998-8): float() instead of eval() in
Parser.GetImagePosition() and Parser.GetImageLocation()
(invesalius/reader/dicom.py).
* debian/control (from unstable 3.1.99998-9): python3-six added to the
Depends of the invesalius binary package.
* debian/patches/series and debian/changelog updated.
[ Other info ]
The CVE-2024-44825 patch went into unstable through salsa merge request
med-team/invesalius!3. invesalius is not in forky at the moment;
3.1.99998-10 is waiting to migrate. 3.1.99998-10 drops the six import
from the code instead of depending on python3-six; this update keeps the
one-line packaging fix from 3.1.99998-9, which leaves the code as it is
in trixie. There is no debian/trixie branch on salsa; I can open a merge
request against one if the team creates it.
I am not a Debian member, so the upload will need a sponsor from the
Debian Med team.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20261117/e39deeb2/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invesalius_3.1.99998-7+deb13u1_trixie.debdiff
Type: application/octet-stream
Size: 7162 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20261117/e39deeb2/attachment-0001.obj>
More information about the Debian-med-packaging
mailing list