swagger-api / swagger-api/swagger-codegen
WS-2014-0065 (High) detected in jna-platform-4.5.0.jar
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
WS-2014-0065 - High Severity Vulnerability
Vulnerable Library - jna-platform-4.5.0.jar
Java Native Access Platform
Library home page: https://github.com/java-native-access/jna
Path to dependency file: /samples/client/petstore-security-test/scala/build.gradle
Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/net.java.dev.jna/jna-platform/4.5.0/ab163522ed76eb01c8c9a750dedacb134fc8c0/jna-platform-4.5.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/net.java.dev.jna/jna-platform/4.5.0/ab163522ed76eb01c8c9a750dedacb134fc8c0/jna-platform-4.5.0.jar
Dependency Hierarchy:
- zinc_2.12-1.3.5.jar (Root Library)
- zinc-compile-core_2.12-1.3.5.jar
- io_2.12-1.3.0.jar
- ❌ jna-platform-4.5.0.jar (Vulnerable Library)
- io_2.12-1.3.0.jar
- zinc-compile-core_2.12-1.3.5.jar
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branch: master
Vulnerability Details
JNA prior to 5.0.0 was discovered to contain an out-of-bounds read. Advapi32Util.registryGetValues does not terminate the returned string with null terminators. When it tries to identify the string content it searches for the next null-terminator and will read out-of-bounds of the buffer.
Publish Date: 2014-06-24
URL: WS-2014-0065
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Release Date: 2014-06-24
Fix Resolution (net.java.dev.jna:jna-platform): 5.0.0
Direct dependency fix Resolution (org.scala-sbt:zinc_2.12): 1.4.0
- Check this box to open an automated fix PR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with samples/client/petstore-security-test/scala/build.gradle and inspect how zinc_2.12 brings in jna-platform 4.5.0. Check the dependency upgrade options listed in the issue, then run the relevant Gradle checks for that sample; done means the vulnerable JNA version is no longer resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100