java-native-access / java-native-access/jna
linjnidispatch.so contains unsafety compilation options
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
-
Version of JNA and related jars
jna-5.5.0.jar -
Version and vendor of the java virtual machine
sun jdk1.8 -
Operating system
Windows 10 Professional -
System architecture (CPU type, bitness of the JVM)
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz 3.00 GHz Bitness of the JVM:32 -
Complete description of the problem
During binary security scanning, the integrated linjnidispatch.so file of the binary file jna-5.5.0.jar has not open some safety compilation options, such as BIND_NOW, NX, PIC, PIE, RELRO, SP, NO Rpath/Runpath, FS, Ftrapv, and Strip. -
Steps to reproduce
binary security scanning
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the binary security scan against jna-5.5.0.jar and inspecting the embedded linjnidispatch.so. Trace the native build configuration that produces this artifact and compare its options with the reported BIND_NOW, NX, PIC, PIE, RELRO, SP, NO Rpath/Runpath, FS, Ftrapv, and Strip requirements. Done means the scan no longer reports missing safety compilation options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100