Extreme FeedbackApplication · Jenkins
CVE-2022-41242
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA missing permission check in Jenkins extreme-feedback Plugin 1.7 and earlier allows attackers with Overall/Read permission to discover information about job names attached to lamps, discover MAC and IP addresses of existing lamps, and rename lamps.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMissing permission check in Jenkins extreme-feedback Plugin versions 1.7 and earlier allows authenticated users with only Overall/Read permission (a low-privilege baseline permission) to enumerate job names attached to lamps, discover network configuration details (MAC/IP addresses), and modify lamp names—exposing sensitive information and enabling unauthorized configuration changes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Extreme FeedbackApplication
<= 1.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if extreme-feedback plugin is installedNavigate to Jenkins Manage Jenkins > Manage Plugins > Installed tab and search for 'extreme-feedback', or use the Jenkins script console with: Jenkins.instance.pluginManager.plugins.findAll { it.shortName == 'extreme-feedback' }Affected if The plugin appears in the installed list
-
Identify the installed version numberIn the plugin manager Installed tab, locate the extreme-feedback plugin and note the Version column; alternatively, check the manifest file in JENKINS_HOME/plugins/extreme-feedback/META-INF/MANIFEST.MFAffected if Version is 1.7 or earlier (e.g., 1.7, 1.6, 1.5, etc.)
-
Verify Overall/Read permission is enabledGo to Jenkins > Manage Jenkins > Manage Users > click on a user > check if Overall/Read permission is checked, or check matrix authorization settings under Manage Jenkins > Configure Global SecurityAffected if Overall/Read permission is granted to any user (this is the default baseline permission in Jenkins)
-
Confirm lamp configuration endpoints are accessibleAttempt to access the plugin's lamp-related views (typically at /plugin/extreme-feedback/ or similar paths under your Jenkins root) using a low-privilege account that has only Overall/Read permissionAffected if The pages load without returning a 403 Forbidden error, indicating missing permission checks
You are affected if the extreme-feedback plugin version is 1.7 or earlier AND Overall/Read permission is enabled for any user, allowing enumeration of job names, MAC/IP addresses, and lamp configuration changes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the extreme-feedback Plugin to version 1.8 or later which includes proper permission checks. Until then, restrict Overall/Read permission to only trusted users.
Fix this in Extreme Feedback
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41242 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41242 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data