Skip to content

[pull] master from google:master#164

Merged
pull[bot] merged 1 commit into
threatcode:masterfrom
google:master
Jul 1, 2026
Merged

[pull] master from google:master#164
pull[bot] merged 1 commit into
threatcode:masterfrom
google:master

Conversation

@pull

@pull pull Bot commented Jul 1, 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 : )

This pull request integrates the pam-ipmi project into OSS-Fuzz,
enabling continuous
  fuzzing of its special group password management and encryption logic.

  Summary of Changes

  1. Project Configuration
* Added projects/pam-ipmi/project.yaml with project metadata and contact
information.
* Added projects/pam-ipmi/Dockerfile to install build-time dependencies
(libpam0g-dev,
     libssl-dev, meson, ninja-build) and prepare the build environment.

  2. Build & Integration
   * Added projects/pam-ipmi/build.sh to:
* Compile src/pam_ipmisave/pam_ipmisave.c with address sanitizer
instrumentation.
       * Link the fuzzer harness against libcrypto and libpam.
       * Package the seed corpus for the fuzzing engine.

  3. Fuzzer Harness
   * Added projects/pam-ipmi/pam_ipmi_fuzzer.c:
* Targets update_pass_special_file, the core logic responsible for
parsing,
decrypting, updating, and re-encrypting the IPMI special password file
         (/etc/ipmi_pass).
* Mocks file system locks (lckpwdf/ulckpwdf) to allow safe execution
within the
         fuzzing container.
* Provides a structured input split to exercise different usernames,
passwords, and
         initial file states.

  4. Seed Corpus
* Added projects/pam-ipmi/corpus/seed1, containing a valid
metapassstruct header to
assist the fuzzer in reaching the deeper decryption and modification
logic.

  Coverage Impact
Local coverage analysis shows that the fuzzer currently exercises the
early parsing and
error-handling paths of the target function. Fixing the identified
buffer overflow will
allow the fuzzer to penetrate the remaining ~80% of the code, including
the
  OpenSSL-based encryption and decryption routines.
@pull pull Bot locked and limited conversation to collaborators Jul 1, 2026
@pull pull Bot added the ⤵️ pull label Jul 1, 2026
@pull pull Bot merged commit d3468c5 into threatcode:master Jul 1, 2026
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.

1 participant