plugin-security-fuzzing
Skill0 starsChanged 23 days agoMITView on GitHub
Use when auditing or hardening an audio plugin: hostile preset and file input, libFuzzer on setStateInformation, sanitizer CI, decoder CVEs, host sandboxing facts, hardening flags, signing.
In this repository69 other files it gives its agents.
- ableton-liveSkill
- ableton-push-expertSkill
- ardourSkill
- arduino-electronics-solderingSkill
- audacitySkill
- audio-driver-stacksSkill
- audio-interface-digital-ioSkill
- av-receiver-specialistSkill
- bazzite-kde-linuxSkill
- bitwig-studioSkill
- color-palette-expertSkill
- couch-pc-cec-gaming-modeSkill
- cubaseSkill
- daw-hubSkill
- denon-prime-sc5000-x1800Skill
- design-software-guideSkill
- dj-gig-guideSkill
- dj-specialistSkill
- drawing-tabletsSkill
- dsp-references-and-licencesSkill
- electronic-music-producerSkill
- fl-studioSkill
- fx-plugin-designSkill
- gha-supply-chain-hardeningSkill
- github-for-beginnersSkill
- github-repo-lockdownSkill
- grapheneosSkill
- graphic-design-expertSkill
- hard-dance-productionSkill
- hardstyle-sound-design-notesSkill
- hardware-protocol-captureSkill
- home-network-specialistSkill
- js-to-cpp-dsp-portSkill
- juce-audio-thread-handoffSkill
- juce-expertSkill
- juce-headless-test-snapshotSkill
- knulli-handhelds-m8Skill
- korg-logue-sdk-expertSkill
- linux-audio-productionSkill
- linux-expertSkill
- linux-security-hardeningSkill
- linux-terminal-expertSkill
- logic-proSkill
- loudness-and-lowend-deliverySkill
- man-page-expertSkill
- max-for-live-expertSkill
- mockup-is-the-pluginSkill
- mockup-to-juce-layoutSkill
- nextcloud-specialistSkill
- photo-editing-color-gradingSkill
- pihole-raspberry-piSkill
- plugin-dsp-qualitySkill
- plugin-fleet-auditSkill
- plugin-performance-profilingSkill
- plugin-ship-checklistSkill
- pro-toolsSkill
- reaperSkill
- rog-ally-x-bazziteSkill
- sound-engineer-acousticsSkill
- sound-forgeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Run it as a short CI job (a few minutes) on the pure C++ engine first (no JUCE needed), then on the processor.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Audio plugin security and robustness
Companion to vst-maker section 11, plugin-ship-checklist and gha-supply-chain-hardening. Labels: VERIFIED (source page), COMMUNITY (forum or secondary source), UNVERIFIED (background knowledge, test first). Research date: November 2026.
What a plugin is
- Native code with the full rights of the user. Host sandboxing is crash isolation, not a security boundary. COMMUNITY. Bitwig hosts plugins out of process by default (crash protection). VERIFIED (bitwig.com). REAPER can isolate per plugin (forum sources). Ardour deliberately does not sandbox. VERIFIED (ardour.org). Ableton and Logic load plugins in process. UNVERIFIED.
Hostile input classes (treat all as parsers of untrusted data)
setStateInformation, presets, imported files: out of bounds reads, trusted size fields, XML and JSON parsing, path traversal in sample or preset loading. Real world example class: a plugin state restore crashing Logic on Apple silicon. COMMUNITY (JUCE forum).- Audio decoders: libsndfile has a long CVE history (FLAC, Vorbis, AIFF, RF64, PCM and MS-ADPCM overflows, WAV writer). COMMUNITY (Arch security tracker data). Pin current versions; JUCE's bundled FLAC and Ogg code only updates when you upgrade JUCE. UNVERIFIED for libFLAC and libvorbis CVE lists.
- Rules: version tag in every state blob; clamp every parameter; length check before every read; never trust a size field; refuse
..and symlinks in user supplied paths; useFile::createTempFilein a private folder; never write next to the user's audio. UNVERIFIED practice.
Fuzzing recipe (no public JUCE plugin harness was found)
- A libFuzzer target that feeds arbitrary bytes to
setStateInformation, preset load and file import:-fsanitize=fuzzer,address,undefined. - Run it as a short CI job (a few minutes) on the pure C++ engine first (no JUCE needed), then on the processor.
- Seed with real states and presets. Keep crashing inputs as regression tests.
- Separate job: ThreadSanitizer for message thread vs audio thread races. pluginval for state round trips.
- Our pure C++ engine tests already run headless; add
-fsanitize=address,undefinedto them first. UNVERIFIED that every repo does.
Build hardening
- Linux:
-fstack-protector-strong,-D_FORTIFY_SOURCE=2,-fPIE,-Wl,-z,relro,-z,now. MSVC:/GS /guard:cf /DYNAMICBASE /sdl. Clang CFI with LTO is awkward with dlopen. UNVERIFIED. - Pin dependencies to commit SHAs (see
gha-supply-chain-hardening).
Signing and licences
- Windows: SignPath Foundation signs OSI licensed projects for free (MFA required, credit line, approval not guaranteed). COMMUNITY (signpath.org). Azure Artifact Signing: individuals only in the US and Canada, organizations in the US, Canada, EU, UK. COMMUNITY.
- macOS: paid Developer ID plus notarization. Never tell users to disable Gatekeeper.
- JUCE is AGPLv3 or commercial; a free open source plugin under AGPLv3 is fine. COMMUNITY. The VST3 SDK reportedly became MIT (3.8.0); check your JUCE version. COMMUNITY, partly conflicting.
Privacy and updates
- Collect nothing: no telemetry, usernames, host names, paths, audio, fingerprints. No auto updater; at most a link to a signed release page. Never download and run code. UNVERIFIED practice, our policy.
Repo side
- Fork only policy and renewal: see
github-repo-lockdown. Private vulnerability reporting invites reports and spam; GitHub added rate limits for them in October 2026. COMMUNITY (changelog summary).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

