CVE-2022-20614
MEDIUMCVE-2022-20614 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:mailer. O3 Security confirms whether CVE-2022-20614 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Incorrect Permission Assignment for Critical Resource in Jenkins Mailer Plugin
Real-World Exposure
org.jenkins-ci.plugins:mailer☕org.jenkins-ci.plugins:mailerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A missing permission check in Jenkins Mailer Plugin 391.ve4a_38c1b_cf4b_ and earlier allows attackers with Overall/Read access to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:mailer | ≥ 391.ve4a38c1bcf4b&&< 408.vd726a | 408.vd726a |
| ☕Maven | org.jenkins-ci.plugins:mailer | all versions | 1.34.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:mailer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins:mailer to 408.vd726a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20614 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-20614 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-20614. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-20614 in your dependencies?
O3 detects CVE-2022-20614 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.