Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
In the Okta Java SDK, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. Affected product and versions You may be affected if you meet the following preconditions: - Using the Okta Java SDK between versions 11.0.0 and 20.0.0, and - Implementing a multithreaded application with the ApiClient class where the response status code is used in access control flows Resolution Upgrade Okta/okta-sdk-java to versions 21.0.0 or greater.
Recommended action: Upgrade to 20.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In the Okta Java SDK, specific multithreaded implementations may encounter memory issues as threads are not properly cleaned up after requests are completed. Over time, this can degrade performance and availability in long-running applications and may result in a denial-of-service condition under sustained load. Affected product and versions You may be affected by this vulnerability if you meet the following preconditions: - Using the Okta Java SDK between versions 21.0.0 and 24.0.0, and - Implementing a long-running application using the ApiClient in a multi-threaded manner. Resolution Upgrade Okta/okta-sdk-java to versions 24.0.1 or greater. Acknowledgement Okta would like to thank Andrew Pikler (pyckle) for their discovery and responsible disclosure.
Recommended action: Upgrade to 24.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.