GHSA-jfh8-c2jp-5v3q
jdk8u
GHSA-jfh8-c2jp-5v3q | jdk8u | |
---|---|---|
9 | 6 | |
- | 201 | |
- | 1.0% | |
- | 8.5 | |
- | 16 days ago | |
Java | ||
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GHSA-jfh8-c2jp-5v3q
- GLPI IS NOT affected by the Log4j vulnerability CVE-2021-44228
-
Ghidra 10.1 Released
Includes fix for CVE-2021-44228 (https://github.com/advisories/GHSA-jfh8-c2jp-5v3q)
- Is this something that effects mining machines as well ? Any miner that can enlighten me about this problem?
- Warning for people playing on Minecraft servers. This is important!
- Security Issue - Minecraft 1.18.1 Release Candidate 3 Is Out!
-
WARNING: DO NOT LOG ONTO PUBLIC SERVERS, NEW ZERO-DAY SECURITY VULNERABILITY FOUND FOR 1.7-1.18
GitHub posted an advisory heres the link and proof-of-concept for those of you interested. https://github.com/advisories/GHSA-jfh8-c2jp-5v3q
- Remote code injection in Log4j
- Log4j RCE Found
jdk8u
-
Seeing through hardware counters: a journey to threefold performance increase
Would an atomic mutable subclass cache (not sure what it's used for, downcasting?) be unnecessary in a language built around static rather than dynamic dispatch by default, like C/C++/Rust and perhaps Go? Or would it still speed up dynamically dispatched code, but is less practical or worthwhile so it isn't used in practice? (Though Rust's Arc also suffers from atomic contention similar to this blog post, when used across dozens of threads: https://pkolaczk.github.io/server-slower-than-a-laptop/)
Also it's somewhat ironic that the JVM source code (https://github.com/openjdk/jdk8u/blob/jdk8u352-b07/hotspot/s...) says "This code is rarely used, so simplicity is a virtue here" at the site of a bottleneck.
-
Minecraft 1.8.9 Consistently Crashes after 5 Mins
Use the latest JDK (Developer's Kit) or JRE (Runtime Environment) for Java 8, compiled and distributed by AdoptOpenJDK from the official Read-Only source.
-
How are LTS updates made?
The majority of the work on 8u, 11u, 17u releases happens in OpenJDK upstream, in so called JDK Updates Projects, by engineers from the interested JDK vendors. You can get a peek who does this kind of work from the repository histories, for example the most recent 11.0.13 is done by engineers from Red Hat (including yours truly), SAP, Azul, Microsoft, BellSoft, Tencent, Amazon, Alibaba, IBM, ARM, Google.
-
Log4Shell Log4j vulnerability (CVE-2021-44228) – cheat-sheet reference guide
> whatever it returned would just get inserted as a string into the log output, no big deal.
Once you can inject anything that gets resolved, you have an information disclosure vulnerability unrelated to the RCE.
If I can just DNS resolve any ${env} variable from the JVM, a lot of systems are compromised by just exposing the env or system variables configured for runtime.
Just getting your $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY env vars can compromise your bucket (sure, that is a really unsafe setup now, but it was almost the standard a few years ago over configuring it explicitly).
So a logging system which will merely resolve a hostname derived from a variable was bad enough to compromise many systems.
The serialization loophole was fixed in a jdk8 update.
https://github.com/openjdk/jdk8u/commit/006e84fc77a582552e71...
But even with that in place, the information disclosure of java System or env properties is bad enough to break actual systems in prod.
-
Log4j RCE Found
> Turns out, by including "." in some part of the URL to this remote class, Log4j lets off its guard & simply looks up to that server and dynamically loads the class file.
No it doesn't. That was disabled by default in 2009, and was disabled by default in every release of Java 8 or later: https://github.com/openjdk/jdk8u/commit/006e84fc77a582552e71...
Unless i am mistaken, i don't believe the attack as described by LunaSec actually works against a default-configured JVM released any time in the last decade.
What are some alternatives?
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
jdk8u_jdk
tsunami-security-scanner-plugins - This project aims to provide a central repository for many useful Tsunami Security Scanner plugins.
apache-log4j-poc - Apache Log4j 远程代码执行
logging-log4j1 - Apache log4j1
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
log4shell - Operational information regarding the log4shell vulnerabilities in the Log4j logging library.
openjdk8-upstream-binaries - Archived release scripts/releases of OpenJDK 8u project builds. Superseded by Eclipse Temurin releases.
FizzBuzz Enterprise Edition - FizzBuzz Enterprise Edition is a no-nonsense implementation of FizzBuzz made by serious businessmen for serious business purposes.
lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/
terminal-escape-injections - A repository dedicated to terminal escape injections.
marshalsec