cve.bz

CVE-2018-1000411 jenkins junit: Cross Site Reference Forgery

6.5 mediumEPSS 0.8%Fix available

Medium (6.5) in jenkins junit. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.jenkins-ci.plugins:junit 1.26.

On this page
A cross-site request forgery vulnerability exists in Jenkins JUnit Plugin 1.25 and earlier in TestObject.java that allows setting the description of a test result.

Severity

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.jenkins-ci.plugins:junit (Maven): fixed in 1.26

Ask an AI about this CVE

Show the promptExplain CVE-2018-1000411 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-1000411?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-1000411?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-1000411 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jenkins:junitthrough 1.25

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x9gm-m8pp-54vxMavenorg.jenkins-ci.plugins:junit<1.261.26

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

For Openshift, Jenkins is used within the infrastructure and deployment in OCP. The package is delivered within the technology but not used by default in production environments. It requires additional configuration in running environments which would be mainly use on testing applications being deployed.

The update is in the latest version released with Red Hat OpenShift 3.11.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 3.10jenkins-2-pluginsWill not fix
Red Hat OpenShift Container Platform 3.11jenkins-2-pluginsWill not fix
Red Hat OpenShift Container Platform 3.3jenkins-plugin-junitWill not fix
Red Hat OpenShift Container Platform 3.4jenkins-plugin-junitWill not fix
Red Hat OpenShift Container Platform 3.5jenkins-plugin-junitWill not fix
Red Hat OpenShift Container Platform 3.6jenkins-2-pluginsWill not fix
Red Hat OpenShift Container Platform 3.7jenkins-2-pluginsWill not fix
Red Hat OpenShift Container Platform 3.9jenkins-2-pluginsWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2018-1000411.

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON