Slide 11 of 27
Part 2 · TypesSlide 11
Slide 11 · Proprietary Algorithm Exposure — Real Example
Proof Pudding — the spam filter that taught attackers how to beat it.
Confirmed Vulnerability · CVE-2019-20634 · CVSS 3.1: 3.7 (Low)
Proof Pudding: Model Extraction Against Proofpoint Email Protection
CVE-2019-20634 · Researchers: Will Pearce & Nick Landers · DerbyCon 2019

The setup: Proofpoint's email protection system scores every incoming email and labels it spam if the score is too low. Those scores were visible in email headers.

The attack: Researchers Will Pearce and Nick Landers collected enough of these scores to train a “copy-cat” machine learning model that mimicked Proofpoint's classifier — without ever touching Proofpoint's source code or training data directly.

The result: With a working copy of the model's decision logic, attackers could craft malicious emails specifically engineered to score well and slip past the real filter.

Why it matters for LLM02: this is a model inversion / extraction attack — exposing enough of a model's outputs let attackers reconstruct its internal logic. OWASP cites this as its canonical example of “Proprietary Algorithm Exposure.”
The Defense This Would Have Stopped

Differential privacy on exposed scores (add noise so raw values can't be cleanly reverse-engineered) plus access controls that rate-limit how many scored queries any one source can make.

← BackNext → Business Data Disclosure