From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] fribidi: Update to version 1.0.18
Date: Wed, 4 Nov 2026 14:49:59 +0100 [thread overview]
Message-ID: <20261104135004.2059527-7-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261104135004.2059527-1-adolf.belka@ipfire.org>
- Update from version 1.0.17 to 1.0.18
- No change in rootfile
- Although there are no CVE's specified, the changelog does mention security fixes
coming from an automated Anthropic OSS Scanner.
- Changelog
1.0.18
* Security and robustness fixes found by an automated scan (Anthropic's
OSS Scanner):
- fribidi_remove_bidi_marks(): fixed an out-of-bounds write before the
caller's map when the position maps returned by one call are passed to
a second call. The maps it returns are now correct, and removed
characters are -1.
- Fixed unchecked memory allocations in fribidi_reorder_line(),
fribidi_log2vis() and the bracket pairing code, which could crash
when memory ran out instead of returning failure.
- Fixed an out-of-bounds read in the CapRTL decoder on platforms where
plain char is unsigned (e.g. aarch64, arm, ppc64le, s390x).
- Fixed quadratic running time on paragraphs made of many back-to-back
isolates, and on deeply nested isolates containing brackets (N0).
* Fixed a stack buffer overflow in the CapRTL/UTF-8 output of fribidi and
fribidi-caprtl2utf8, and an integer overflow in the run-pool allocation
on 32-bit platforms.
* Fixed paragraph direction detection to reset isolates at paragraph
boundaries.
* Bidi fixes to match UAX #9 more closely. These can change the output for
unusual input:
- Overflow isolates are no longer treated as valid isolates (X5a-X5c),
and PDF handling checks the overflow counts first (X7).
- Bracket pairs (BD16/N0) no longer pair across isolates, and a full
bracket stack no longer stops pairing outside its isolating run
sequence.
* fribidi_unicode_to_charset() now null-terminates the output for an
unknown character set.
* Added regression tests and a fuzzing seed.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/fribidi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/fribidi b/lfs/fribidi
index f215cc0ce..29e43050e 100644
--- a/lfs/fribidi
+++ b/lfs/fribidi
@@ -24,7 +24,7 @@
include Config
-VER = 1.0.17
+VER = 1.0.18
THISAPP = fribidi-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 5e2fdef3c47e12af85b2e8d7a9d421a3e9a0f1a92e36bee267a45960c8f3cdc0628011d301d9f0f02ce68bf7007ad14fa4520a41da4a8e3d09483b5e50e83a57
+$(DL_FILE)_BLAKE2 = 7e4d34e860ae46ee3ed1c9096903981a88f515fbb175d8e7f924a6053f86942d549101990e1c05dcf3fdd4a4b65efae7831a2e7f99cb7bfcc5d7ab9b5c4f2137
install : $(TARGET)
--
2.56.0
next prev parent reply other threads:[~2026-11-04 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 13:49 [PATCH] aprutil: Update to version 1.6.6 Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship aprutil Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship fribidi Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship kmod Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship libjpeg Adolf Belka
2026-11-04 13:49 ` [PATCH] core207: Ship nano Adolf Belka
2026-11-04 13:49 ` Adolf Belka [this message]
2026-11-04 13:50 ` [PATCH] kmod: Update to version 34.3 Adolf Belka
2026-11-04 13:50 ` [PATCH] libarchive: Update to version 3.8.11 Adolf Belka
2026-11-04 13:50 ` [PATCH] libjpeg: Update to version 3.2.1 Adolf Belka
2026-11-04 13:50 ` [PATCH] nano: Update to version 9.3 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261104135004.2059527-7-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox