From 8696d130ec36a11bc5c11016735624645167f6f3 Mon Sep 17 00:00:00 2001
From: "advisory-database[bot]"
 <45398580+advisory-database[bot]@users.noreply.github.com>
Date: Thu, 15 May 2025 21:26:15 +0000
Subject: [PATCH] Publish GHSA-66fw-43h8-f8p3

---
 .../2024/07/GHSA-66fw-43h8-f8p3/GHSA-66fw-43h8-f8p3.json      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/advisories/github-reviewed/2024/07/GHSA-66fw-43h8-f8p3/GHSA-66fw-43h8-f8p3.json b/advisories/github-reviewed/2024/07/GHSA-66fw-43h8-f8p3/GHSA-66fw-43h8-f8p3.json
index f6b903dcd67..597b8a84f75 100644
--- a/advisories/github-reviewed/2024/07/GHSA-66fw-43h8-f8p3/GHSA-66fw-43h8-f8p3.json
+++ b/advisories/github-reviewed/2024/07/GHSA-66fw-43h8-f8p3/GHSA-66fw-43h8-f8p3.json
@@ -1,11 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-66fw-43h8-f8p3",
-  "modified": "2024-07-26T21:14:54Z",
+  "modified": "2025-05-15T21:23:42Z",
   "published": "2024-07-26T21:14:54Z",
   "aliases": [],
   "summary": "XMP Toolkit's `XmpFile::close` can trigger undefined behavior",
-  "details": "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.\n\nThis is best demonstrated in [issue #230](https://github.com/adobe/xmp-toolkit-rs/issues/230), where a race condition causes the `close` call to fail due to file I/O errors.\n\nThis was fixed in [PR #232](https://github.com/adobe/xmp-toolkit-rs/pull/232) (released as crate version 1.9.0), which now safely handles the exception.\n\nFor 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.\n\nUsers of all prior versions of `xmp_toolkit` are encouraged to update to version 1.9.0 to avoid undefined behavior.\n",
+  "details": "Affected versions of the crate failed to catch C++ exceptions raised within the `XmpFile::close` function. If such an exception occurred, it would trigger undefined behavior, typically a process abort.\n\nThis is best demonstrated in [issue #230](https://github.com/adobe/xmp-toolkit-rs/issues/230), where a race condition causes the `close` call to fail due to file I/O errors.\n\nThis was fixed in [PR #232](https://github.com/adobe/xmp-toolkit-rs/pull/232) (released as crate version 1.9.0), which now safely handles the exception.\n\nFor 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.\n\nUsers of all prior versions of `xmp_toolkit` are encouraged to update to version 1.9.0 to avoid undefined behavior.",
   "severity": [],
   "affected": [
     {