xmp_toolkit
Affected
- introduced
0.0.0-0, fixed1.9.0(semver)
Fixed versions
1.9.0
Fix
- Fixed version
1.9.0cargo update -p xmp_toolkit --precise 1.9.0
Advisory
Also known as: GHSA-66fw-43h8-f8p3
XmpFile::close can trigger UB
Affected versions of the crate failed to catch C++ exceptions raised within the XmpFile::close function. If such an exception occured, it would trigger undefined behavior, typically a process abort.
This is best demonstrated in issue #230, where a race condition causes the close call to fail due to file I/O errors.
This was fixed in PR #232 (released as crate version 1.9.0), which now safely handles the exception.
For backward compatibility, the existing API ignores the error. A new API XmpFile::try_close was added to allow callers to receive and process the error result.
Users of all prior versions of xmp_toolkit are encouraged to update to version 1.9.0 to avoid undefined behavior.
Not rated by the source.
0.0.0-0, fixed 1.9.0 (semver)1.9.0
1.9.0cargo update -p xmp_toolkit --precise 1.9.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0