This update for jline3 fixes the following issue:
Update to upstream version 3.30.17:
* Security Fixes
+ Native Stack Buffer Overflow in Public INPUT_RECORD.memmove
JNI Method (Windows) (GHSA-6r3w-6jpj-x5w6)
+ Authenticated SSH Shell Channel Resource Leak via Null or
Non-Numeric PTY Dimensions (GHSA-7h86-pjwh-gpqj)
+ Authenticated SSH DoS via Unbounded Window-Change Terminal
Geometry (GHSA-m935-wqpj-pvp3)
+ TCP Socket File Descriptor Leak When Maximum Connections
Reached (GHSA-c87g-867h-cqr6)
* Bug Fixes
+ strip control characters from file names in posix builtins
+ bound !# history expansion to prevent exponential blowup
+ verify server host keys in the ssh client builtin
+ address remaining security vulnerabilities reported by
AFINE/CERT.PL
+ backport security fixes from master
+ backport security fixes to 3.x (path traversal + DSR plain
text)
+ strip control characters from ssh banner and prompts
* Dependency updates
+ bump com.diffplug.spotless:spotless-maven-plugin from 3.8.0 to
3.10.2
+ bump slf4j.version from 2.0.18 to 2.0.19
+ bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.6
to 3.6.0
+ bump org.apache.maven.plugins:maven-compiler-plugin from
3.15.0 to 3.16.0
+ bump org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.2
+ bump actions/setup-java from 5 to 6.0.0
+ bump org.graalvm.sdk:graal-sdk from 25.1.3 to 25.3.4.1
+ bump com.mycila:license-maven-plugin from 5.0.0 to 5.1.2
+ bump org.easymock:easymock from 5.6.0 to 5.7.0
+ bump com.google.jimfs:jimfs from 1.3.1 to 1.3.2
+ bump org.apache.maven.wrapper:maven-wrapper from 3.3.2 to
3.3.4
+ bump org.apache.maven:apache-maven from 4.0.0-rc-3 to
4.0.0-rc-6
+ bump eu.maveniverse.maven.njord:extension3 from 0.9.9 to
0.9.10
+ bump com.palantir.javaformat:palantir-java-format from 2.96.0
to 2.97.0
+ bump release-drafter/release-drafter from 7.6.0 to 7.7.0
+ bump groovy.version from 4.0.32 to 4.0.33
+ bump release-drafter/release-drafter from 7 to 7.6.0
+ bump org.apache.maven.plugins:maven-jar-plugin from 3.5.0 to
3.5.1
- Update to upstream version 3.30.16
* bugfix release with security hardening, SSH agent forwarding
fix, and terminal compatibility improvements.
* Breaking Changes
+ SSH agent forwarding is no longer enabled by default;
pass -A to explicitly request it
+ reject overlong hex components in OSC color responses
+ strip OSC and other escape sequences in ansiAppend
+ search multiple lib paths for versioned libutil.so
+ use Path.resolve instead of URI.resolve in cat and sort to
prevent SSRF
+ check closed flag in PtyInputStream to prevent hang on empty
input
+ confine ConfigurationPath lookups to the config directory
+ disable Read File command in nano restricted mode
+ drain buffered data before EOF in NonBlockingPumpInputStream
+ look up openpty in libc.so.6 for glibc 2.34+
+ guard styleMatches and highlighter rules against ReDoS
+ backport telnet DoS mitigations (GHSA-47qp, GHSA-2r2c)
+ propagate EOF in PtyInputStream to avoid infinite loop
+ bump org.apache.ivy:ivy from 2.5.3 to 2.6.0
+ bump actions/setup-node from 6 to 7
+ bump com.palantir.javaformat:palantir-java-format from 2.94.0
to 2.96.0
+ bump sshd.version from 2.18.0 to 2.19.0
+ bump org.codehaus.gmavenplus:gmavenplus-plugin from 5.0.0 to
5.1.0
+ bump org.graalvm.sdk:graal-sdk from 25.0.3 to 25.1.3
+ bump com.diffplug.spotless:spotless-maven-plugin
dalance procs versions up to 0.14.12 do not sanitize escape sequences in process command lines before displaying them. This allows local attackers to include malicious ANSI or OSC escape sequences in command line arguments, which are then rendered unmodified on other users' terminals.
Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in ash-project usage_rules allows a malicious package publisher to inject terminal control sequences into the output of mix usage_rules.search_docs.
mix usage_rules.search_docs searches Hex documentation through search.hexdocs.pm, which indexes the documentation of every published package, and prints the matching results (title, package, type, doc reference, and highlighted snippets) to the terminal. The formatter in Mix.Tasks.UsageRules.SearchDocs interpolated those publisher-controlled fields verbatim, neutralizing no terminal control characters; the only transform it applied adds escape sequences rather than removing them. A malicious package can embed ANSI terminal escape sequences (cursor movement, line erase, carriage returns, OSC 52 clipboard writes) in its indexed documentation, so when a developer runs a search that surfaces those docs the sequences reach the terminal unchanged — forging the displayed hexdocs URL or a suggested command, hiding text, or writing to the clipboard. No authentication or privileged position is required; only publishing a package.
This issue affects usage_rules: from 0.1.18 before 1.2.8.
broot renders each file and directory name in its interactive tree view exactly as read from the filesystem. Names are converted with a plain to_string_lossy() call in src/tree_build/builder.rs and in TreeLine::unprune in src/tree/tree_line.rs, and no control-character filtering exists anywhere in the code, even though the doc comment on the TreeLine name field states that some characters may have been stripped. Any local user who can create a file can therefore place an escape sequence in its name and have it written unmodified to the terminal of anyone who browses that directory, between broot's own styling codes. A reported proof of concept used an OSC 52 clipboard-write sequence and captured the raw bytes broot wrote to its pty, confirming the sequence reaches the terminal unstripped. What an injected OSC or CSI sequence can then do depends on the terminal emulator in use. Browsing a directory is broot's primary function and carries no expectation that the content is trusted.
diff‑so‑fancy does not properly sanitize non‑SGR terminal control sequences before outputting diff data. The application only strips ANSI SGR sequences while allowing other control characters, including carriage return (\r) and escape sequences (e.g., OSC, CSI), to pass through unsanitized.
An attacker can embed malicious control sequences in filenames, diff metadata, or file content that are rendered directly in the terminal during diff viewing. This can lead to output manipulation, including filename spoofing, terminal screen clearing, and clipboard injection via supported escape sequences.
Successful exploitation may mislead users during code review, alter terminal state, or result in unintended command execution through clipboard hijacking.
This issue has been fixed in the commit 9c81294
Oh My Posh versions prior to 29.35.1 allow terminal escape sequence injection via unsanitized prompt segment data. This occurs because dynamic strings such as directory names and Git commit metadata are rendered into the prompt without neutralizing raw terminal control characters. An attacker controlling these values can inject ANSI/OSC escape sequences that the victim's terminal executes on every prompt render, enabling clipboard hijacking, prompt spoofing, window-title manipulation, and denial of service.
The npm package @salem_jalal/osc-components version 1981.17.7 contains malicious code that exfiltrates sensitive information. Its postinstall script sends host identifiers to a remote server over unencrypted HTTP. Additionally, when loaded in a browser context, it harvests cookies, localStorage data, the current URL, and user agent details, sending them with credentials to the same remote server. The package impersonates another namespace (@dx-ui) to facilitate dependency confusion attacks.
Claude HUD through 0.0.12, patched in commit 234d9aa, constructs OSC 8 terminal hyperlink escape sequences using raw cwd and branchUrl values without stripping control characters or encoding embedded values, allowing attackers to inject arbitrary ANSI codes into terminal sessions. Attackers can embed ESC+backslash sequences in the current working directory or branch URL to execute malicious ANSI codes including text color changes, forged prompts, and OSC 52 clipboard writes, or trigger outbound HTTP requests to attacker-controlled remotes when hyperlinks are clicked.
Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.233, Tabby before 1.0.233 automatically confirms ZMODEM protocol detection on all terminal session output without user interaction, enabling shell command execution when a user displays attacker-controlled content. The ZModemMiddleware in tabby-terminal consumes all session output through a Zmodem.Sentry, and when a ZMODEM ZRQINIT header is detected, unconditionally calls detection.confirm() and writes a fixed ZRINIT response ( **\x18B0100000023be50\r\n\x11) back into the active PTY as input. When the process that triggered the detection (e.g., cat) exits, the injected bytes are consumed by the user's shell as a command line. Under fish (default configuration), the ** prefix triggers recursive glob expansion against the current directory, allowing an attacker-placed executable at a matching nested path (e.g., d/xB0100000023be50) to be executed by relative pathname without relying on PATH. Under bash and zsh, a secondary xterm.js terminal color-query feedback (OSC 10) can be combined in the same file to inject a slash-containing command word that similarly bypasses PATH resolution. An attacker can exploit this by providing a crafted file (e.g., in a cloned Git repository) that a user displays with cat, achieving code execution with no interaction beyond viewing the file. This vulnerability is fixed in 1.0.233.
Open OnDemand is an open-source high-performance computing portal. The Files application in OnDemand versions prior to 4.0.9 and 4.1.3 is susceptible to malicious input when navigating to a directory. This has been patched in versions 4.0.9 and 4.1.3. Versions below this remain susceptible.
Open OnDemand provides remote web access to supercomputers. In versions 4.0.8 and prior, the Apache proxy allows sensitive headers to be passed to origin servers. This means malicious users can create an origin server on a compute node that record these headers when unsuspecting users connect to it. Maintainers anticipate a patch in a 4.1 release. Workarounds exist for 4.0.x versions. Using `custom_location_directives` in `ood_portal.yml` in version 4.0.x (not available for versions below 4.0) centers can unset and or edit these headers. Note that `OIDCPassClaimsAs both` is the default and centers can set `OIDCPassClaimsAs ` to `none` or `environment` to stop passing these headers to the client. Centers that have an OIDC provider with the `OIDCPassClaimsAs` with `none` or `environment` settings can adjust the settings using guidance provided in GHSA-2cwp-8g29-9q32 to unset the mod_auth_openidc_session cookies.
### Impact
A specially crafted argument to the `idna.encode()` function could consume significant resources. This may lead to a denial-of-service.
### Patches
The function has been refined to reject such strings without the associated resource consumption in version 3.7.
### Workarounds
Domain names cannot exceed 253 characters in length, if this length limit is enforced prior to passing the domain to the `idna.encode()` function it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.
### References
* https://huntr.com/bounties/93d78d07-d791-4b39-a845-cbfabc44aadb