What is the severity of CVE-2018-1999026?

CVE-2018-1999026 has been assigned a medium severity rating due to its potential for server-side request forgery.

How do I fix CVE-2018-1999026?

To fix CVE-2018-1999026, upgrade the Jenkins TraceTronic ECU-TEST Plugin to version 2.4 or later.

What are the exploits associated with CVE-2018-1999026?

CVE-2018-1999026 can be exploited by attackers to send unauthorized HTTP requests to an attacker-controlled server.

Which versions of Jenkins are affected by CVE-2018-1999026?

Jenkins TraceTronic ECU-TEST Plugin versions 2.3 and earlier are affected by CVE-2018-1999026.

How can I determine if I am affected by CVE-2018-1999026?

You are affected by CVE-2018-1999026 if you are using Jenkins with the TraceTronic ECU-TEST Plugin version 2.3 or earlier.

Vulnerability/
CVE-2018-1999026

medium

6.5

CWE

918

1/8/2018

5/8/2024

CVE-2018-1999026: SSRF

First published: Wed Aug 01 2018(Updated: )

A server-side request forgery vulnerability exists in Jenkins TraceTronic ECU-TEST Plugin 2.3 and earlier in ATXPublisher.java that allows attackers to have Jenkins send HTTP requests to an attacker-specified host.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Jenkins Tracetronic Ecu-test	<=2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-1999026?
CVE-2018-1999026 has been assigned a medium severity rating due to its potential for server-side request forgery.
How do I fix CVE-2018-1999026?
To fix CVE-2018-1999026, upgrade the Jenkins TraceTronic ECU-TEST Plugin to version 2.4 or later.
What are the exploits associated with CVE-2018-1999026?
CVE-2018-1999026 can be exploited by attackers to send unauthorized HTTP requests to an attacker-controlled server.
Which versions of Jenkins are affected by CVE-2018-1999026?
Jenkins TraceTronic ECU-TEST Plugin versions 2.3 and earlier are affected by CVE-2018-1999026.
How can I determine if I am affected by CVE-2018-1999026?
You are affected by CVE-2018-1999026 if you are using Jenkins with the TraceTronic ECU-TEST Plugin version 2.3 or earlier.

collector/nvd-index
agent/references
agent/softwarecombine
agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/author
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/tags
agent/source
vendor/jenkins
canonical/jenkins tracetronic ecu-test
version/jenkins tracetronic ecu-test/2.3

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-1999026?
CVE-2018-1999026 has been assigned a medium severity rating due to its potential for server-side request forgery.
How do I fix CVE-2018-1999026?
To fix CVE-2018-1999026, upgrade the Jenkins TraceTronic ECU-TEST Plugin to version 2.4 or later.
What are the exploits associated with CVE-2018-1999026?
CVE-2018-1999026 can be exploited by attackers to send unauthorized HTTP requests to an attacker-controlled server.
Which versions of Jenkins are affected by CVE-2018-1999026?
Jenkins TraceTronic ECU-TEST Plugin versions 2.3 and earlier are affected by CVE-2018-1999026.
How can I determine if I am affected by CVE-2018-1999026?
You are affected by CVE-2018-1999026 if you are using Jenkins with the TraceTronic ECU-TEST Plugin version 2.3 or earlier.