What is the severity of CVE-2019-4008?

CVE-2019-4008 is considered a medium severity vulnerability due to the potential for access token leaks.

How does CVE-2019-4008 impact API Connect?

CVE-2019-4008 allows authorization tokens to be inadvertently logged, creating a risk of exposure.

How do I fix CVE-2019-4008?

To remediate CVE-2019-4008, upgrade API Connect to a version later than 2018.4.1.1.

Which versions of API Connect are affected by CVE-2019-4008?

CVE-2019-4008 affects IBM API Connect versions from 2018.1.0 up to and including 2018.4.1.1.

What should I do if I suspect my API Connect installation is vulnerable to CVE-2019-4008?

If you suspect your installation is vulnerable to CVE-2019-4008, immediately review your logging practices and consider upgrading to a secure version.

Vulnerability/
CVE-2019-4008

critical

9.8

CWE

532

1/2/2019

7/2/2019

21/11/2024

CVE-2019-4008

First published: Fri Feb 01 2019(Updated: )

API Connect V2018.1 through 2018.4.1.1 is impacted by access token leak. Authorization tokens in some URLs can result in the tokens being written to log files. IBM X-Force ID: 155626.

Credit: psirt@us.ibm.com psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM API Connect	>=2018.1.0<=2018.4.1.1
	>=2018.1.0<=2018.4.1.1

Remedy

https://www.ibm.com/support/docview.wss?uid=ibm10869772

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-4008?
CVE-2019-4008 is considered a medium severity vulnerability due to the potential for access token leaks.
How does CVE-2019-4008 impact API Connect?
CVE-2019-4008 allows authorization tokens to be inadvertently logged, creating a risk of exposure.
How do I fix CVE-2019-4008?
To remediate CVE-2019-4008, upgrade API Connect to a version later than 2018.4.1.1.
Which versions of API Connect are affected by CVE-2019-4008?
CVE-2019-4008 affects IBM API Connect versions from 2018.1.0 up to and including 2018.4.1.1.
What should I do if I suspect my API Connect installation is vulnerable to CVE-2019-4008?
If you suspect your installation is vulnerable to CVE-2019-4008, immediately review your logging practices and consider upgrading to a secure version.

collector/nvd-index
agent/type
agent/remedy
agent/references
agent/weakness
agent/severity
agent/description
agent/first-publish-date
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/author
agent/last-modified-date
agent/softwarecombine
agent/event
agent/tags
agent/source
vendor/ibm
canonical/ibm api connect
version/ibm api connect/2018.1.0
version/ibm api connect/2018.4.1.1

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-2019-4008?
CVE-2019-4008 is considered a medium severity vulnerability due to the potential for access token leaks.
How does CVE-2019-4008 impact API Connect?
CVE-2019-4008 allows authorization tokens to be inadvertently logged, creating a risk of exposure.
How do I fix CVE-2019-4008?
To remediate CVE-2019-4008, upgrade API Connect to a version later than 2018.4.1.1.
Which versions of API Connect are affected by CVE-2019-4008?
CVE-2019-4008 affects IBM API Connect versions from 2018.1.0 up to and including 2018.4.1.1.
What should I do if I suspect my API Connect installation is vulnerable to CVE-2019-4008?
If you suspect your installation is vulnerable to CVE-2019-4008, immediately review your logging practices and consider upgrading to a secure version.