Skip to content

[pull] master from google:master - #192

Merged
pull[bot] merged 5 commits into
threatcode:masterfrom
google:master
Jul 30, 2026
Merged

[pull] master from google:master#192
pull[bot] merged 5 commits into
threatcode:masterfrom
google:master

Conversation

@pull

@pull pull Bot commented Jul 30, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

OSS-Fuzz Team and others added 5 commits July 30, 2026 11:21
Updates LLVM usage to match
[6d1ace547c9f](llvm/llvm-project@6d1ace547c9f)

Indexer-PiperOrigin-RevId: 956634975
The build source map records Apache Thrift as
https://github.com/apache/thrift.git, while `project.yaml` used the
equivalent URL without `.git`. ClusterFuzz compares these URLs exactly
when selecting the main component; the mismatch made it fall back to
alphabetical ordering and report Ruzzy’s revision as the
tested/regressed revision.

Using the canonical .git URL lets ClusterFuzz prioritize Apache Thrift
and report its revision correctly.

https://oss-fuzz.com/testcase-detail/4583322718896128

<img width="2296" height="408" alt="CleanShot 2026-07-30 at 11 59 09@2x"
src="https://github.com/user-attachments/assets/0ab1b338-2196-4eb1-b34d-531141601cbb"
/>
Update jsoup's CSS/HTML fuzzer to treat selector validation failures as
rejected inputs.

jsoup now normalizes re2j runtime pattern-complexity errors into
`ValidationException`. The fuzzer should ignore these expected
validation failures alongside selector parse errors.

Validation:

- `python3 infra/helper.py check_build jsoup CssHtmlFuzzer`
This PR updates the compiler used when building the fuzzers to be the
one provided by the underlying ubuntu image.

Prior to this PR, the build process would use Envoy's hermetic LLVM to
build the fuzzers.
However, the required glibc version by the LLVM is incompatible with the
one provided by the underlying image.
We get the following error:
```
Step #3 - "compile-honggfuzz-address-x86_64": # Execution platform: @@internal_platforms_do_not_use//host:host
Step #3 - "compile-honggfuzz-address-x86_64": external/llvm_toolchain_llvm/bin/clang: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by external/llvm_toolchain_llvm/bin/clang)
Step #3 - "compile-honggfuzz-address-x86_64": external/llvm_toolchain_llvm/bin/clang: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by external/llvm_toolchain_llvm/bin/clang)
Step #3 - "compile-honggfuzz-address-x86_64": external/llvm_toolchain_llvm/bin/clang: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by external/llvm_toolchain_llvm/bin/clang)
Step #3 - "compile-honggfuzz-address-x86_64": external/llvm_toolchain_llvm/bin/clang: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by external/llvm_toolchain_llvm/bin/clang)
Step #3 - "compile-honggfuzz-address-x86_64": external/llvm_toolchain_llvm/bin/clang: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by external/llvm_toolchain_llvm/bin/clang)
Step #3 - "compile-honggfuzz-address-x86_64": external/llvm_toolchain_llvm/bin/clang: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by external/llvm_toolchain_llvm/bin/clang)
```

We tried to upgrade the underlying ubuntu image to v24.04, however other
version incompatibilities were observed.
Add Paul Moore (@pcmoore) and Jason Zaman (@perfinion), both active
SELinux maintainers, to the cc list. These addresses are allegedly
Google mail accounts despite not being @gmail.com; let us know if these
won't work and we will provide gmail ones.

Signed-off-by: Stephen Smalley <stephen.smalley.work@gmail.com>
@pull pull Bot locked and limited conversation to collaborators Jul 30, 2026
@pull pull Bot added the ⤵️ pull label Jul 30, 2026
@pull
pull Bot merged commit 29be6d3 into threatcode:master Jul 30, 2026
16 of 18 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants