Scan indicates java version used is vulnerable to log4j (Trivy)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 549
- Forks
- 277
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Description
| com.splunk.logging:splunk-library-javalogging | GHSA-94g7-hpv8-h9qm | CRITICAL | 1.6.2 | 1.11.1 | Remote code injection in Log4j |
| | | | | | -->github.com/advisories/GHSA-94g7-hpv8-h9qm |
+ +---------------------+----------+ + +----------------------------------------------+
| | GMS-2021-61 | UNKNOWN | | | Improper Neutralization of |
| | | | | | Special Elements used in an OS |
| | | | | | Command ('OS Command...
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 by locating the dependency declaration for com.splunk.logging:splunk-library-javalogging, then run the Trivy scan that produced this report. Confirm how version 1.6.2 is brought into the image and update or otherwise remediate it so the reported Log4j vulnerability is no longer detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100