You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a vulnerability in the Binance Java Connector related to the Okio library. The issue is a "Signed to Unsigned Conversion Error," identified by GitHub Security Advisory GHSA-w33c-445m-f8w7. This vulnerability could pose a security risk in applications using the connector with versions of Okio before 3.0.0.
Steps to Reproduce:
Add the binance-connector-java dependency to your project (pom.xml).
Run an OWASP Dependency Check or similar security tool to analyze your project.
The tool flags the issue due to the use of Okio in the connector, specifically in versions 3.0.x and lower.
Affected Versions:
Binance Java Connector version 3.4.0 and earlier.
Solution:
To resolve the issue, I fixed the vulnerability by enforcing the use of Okio version 3.9.1, which addresses the security concern. Here is the fix I applied to my pom.xml file:
I encountered a vulnerability in the Binance Java Connector related to the Okio library. The issue is a "Signed to Unsigned Conversion Error," identified by GitHub Security Advisory GHSA-w33c-445m-f8w7. This vulnerability could pose a security risk in applications using the connector with versions of Okio before 3.0.0.
Steps to Reproduce:
Affected Versions:
Solution:
To resolve the issue, I fixed the vulnerability by enforcing the use of Okio version 3.9.1, which addresses the security concern. Here is the fix I applied to my pom.xml file:
This forces the project to use Okio version 3.9.1, which is free from the vulnerability.
The text was updated successfully, but these errors were encountered: