---
title: "Discussion on \"Java4Shell: I Ran the Published Trigger on a Vulnerable JDK. It Did Not Fire.\" | Hashnode"
description: "Discussion on \"Java4Shell: I Ran the Published Trigger on a Vulnerable JDK. It Did Not Fire.\". The headline version of Java4Shell is simple: a malformed Base64 string, 64 A characters followed by =, corrupts memory in OpenJDK, and from there the researchers at Calif reached remote code executio"
url: "https://hashnode.com/posts/java4shell-i-ran-the-published-trigger-on-a-vulnerable-jdk-it-did-not-fire/6afcff720207d48bb485e18a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Java4Shell: I Ran the Published Trigger on a Vulnerable JDK. It Did Not Fire.](https://aheadkit.hashnode.dev/java4shell-i-ran-the-published-trigger-on-a-vulnerable-jdk-it-did-not-fire?utm_source=hashnode&utm_medium=feed)

The headline version of Java4Shell is simple: a malformed Base64 string, 64 A characters followed by =, corrupts memory in OpenJDK, and from there the researchers at Calif reached remote code executio

18h ago · 5 min read · aheadkit.hashnode.dev  
Read the article

-   [#java](https://hashnode.com/tag/java)
-   [#security](https://hashnode.com/tag/security)
-   [#openjdk](https://hashnode.com/tag/openjdk)
-   [#vulnerability](https://hashnode.com/tag/vulnerability)

## Written by

[Abdus Salam](https://hashnode.com/@aheadkit)

@aheadkit

  
[View profile](https://hashnode.com/@aheadkit)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
