Overview
Overview: When a flaw lands in the Java runtime itself, every Java application running on it is exposed, however well its own code is written. The first questions are always the same: where does Java run in your estate, and which build is actually running? This assessment, built on Firemind's IT Operations Engine, answers both from your AWS account and the repositories that build it. It is free, with no commitment.
Current advisory: Java4Shell (CVE-2026-114938), also reported as Java2Shell. A flaw in the OpenJDK Base64 decoder lets crafted input corrupt memory, often before login, and researchers showed code execution on default installs of Keycloak, Jira, Jenkins and others. It affects OpenJDK-based runtimes from 17.0.6, including 21, 25 and 27, but only on x86-64 processors with AVX-512 VBMI (Intel Ice Lake and later, AMD Zen 4 and later). Graviton is not affected. Fixed builds include Amazon Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4, and Oracle Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. The JVM flag -XX:-UseBASE64Intrinsics is the interim mitigation.
Why one patch is not enough
Servers carry an operating-system package, products bundle their own runtime, and container images keep the JDK they were built with until rebuilt. A running process keeps the old build until it restarts. And because Java4Shell depends on the processor, a resize can bring the exposure back.
What you receive
- An inventory of every Java runtime in scope: Amazon EC2, container images in Amazon ECR running on Amazon ECS, Amazon EKS or AWS Fargate, AWS Lambda functions on Java runtimes or container images, and AWS Elastic Beanstalk Java environments
- The vendor, distribution and build of each runtime, and whether it carries the fix
- A processor check per workload: AVX-512 VBMI instance types first, Graviton and arm64 Lambda marked clear, resize risk flagged
- A reachability ranking: internet-facing identity, CI/CD and collaboration services first, internal-only services last
- A running-versus-deployed check: the image digest actually running compared with the tag you deployed
- Dockerfiles, Maven and Gradle files and base images in your repositories that would put a vulnerable JDK back on the next build
- A fix plan for each finding, with interim mitigations such as the -XX:-UseBASE64Intrinsics JVM flag where an update has to wait
- A readout with a Firemind cloud architect
Two steps, two roles
Step one is the same read-only role as the IT Operations Engine Free Assessment, deployed with Quick Launch. It reads configuration and metadata only, so your data stays out of scope and nothing in your account is changed. If you already run the Free Assessment, this step is already done. Connect GitHub, GitLab or Bitbucket with read-only access so the assessment can read the files that build your workloads.
Step two inspects inside container images and Lambda packages. For security purposes, a Firemind representative will get in contact after you subscribe to update the security rules with your team, in line with your standard operating procedures for code security. This adds a separate CloudFormation stack that you review in full before it runs, scoped to the images, functions and KMS keys you name. Databases, logs, secrets, sessions and commands stay out of scope, enforced by explicit Deny policies.
How it works
- Subscribe here. It is free, no card, no commitment.
- Deploy the read-only role using Quick Launch. It registers with Firemind automatically.
- Connect your source control with read-only access.
- Optionally, enable image and package inspection with a Firemind representative.
- Firemind returns your exposure report and a readout with a Firemind cloud architect.
- Delete either stack whenever you choose. Access ends with it.
Scope: One AWS account and the repositories that build what runs in it. Larger estates are covered by the paid follow-on.
Next step: Java Vulnerability Assessment and Remediation on AWS by Firemind on AWS Marketplace fixes what the assessment finds, under your change rules, and keeps it fixed. Delivered as a private offer.
About Firemind: AWS Premier Tier Services Partner. 200+ clients since 2018, ISO 27001 certified, in partnership with AWS, NVIDIA and Anthropic. Core markets: UK and Ireland, Finland, Germany and the Netherlands.
Highlights
- Finds every Java runtime in your AWS account and code: EC2, container images on ECS, EKS and Fargate, Lambda and Elastic Beanstalk, plus the base images and build files that would bring an old JDK back.
- Checks the chip, not just the version: Java4Shell only runs on x86-64 processors with AVX-512 VBMI, so every workload is placed by instance type, with Graviton marked clear and resize risk flagged.
- Ranked by real exposure: internet-facing identity, CI/CD and collaboration services first, with interim JVM-flag mitigations where an update has to wait.
Details
Features and programs
Financing for AWS Marketplace purchases
Quick Launch
Pricing
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
This product is free. AWS Marketplace collects no fees from you and Firemind does not invoice for it, so there is nothing to refund. You can cancel your subscription at any time in the AWS Marketplace console, and you can revoke Firemind's access immediately by removing the connection you created. If you believe you have been charged for this product in error, contact Firemind at hello@firemind.com and we will respond within one business day.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Additional details
Usage instructions
Use Quick Launch above if you can. These steps are for buyers whose policy is to review and deploy CloudFormation themselves.
What gets created, and nothing else
- One IAM role, FaePlatformRole, which Firemind assumes to run the assessment
- Three IAM managed policies, all of them Deny, layered over the role's baseline
- One execution role and one Lambda function, used once to report the created role ARN back to Firemind, then never invoked again
- One custom resource that invokes that function
What the role can and cannot do
The baseline is the AWS managed SecurityAudit and ViewOnlyAccess policies. Three Deny policies sit over the top, covering object and storage data, database and stream contents, and secrets, key material and privilege escalation. An explicit Deny always wins in IAM evaluation, so this holds regardless of what the baseline would otherwise permit.
The role can list a bucket and count its objects, but cannot read one. It can describe a database, its engine and its encryption configuration, but cannot read a row. It cannot decrypt anything, read a secret or parameter value, download log contents, or open a session to a host. Remediation is disabled and the role holds no write permissions.
Steps
- Download the template from the URL shown in the Quick Launch panel and review it. Everything above is visible in the file.
- Create the stack in any region you like. The role is global, so the region only determines where the stack object lives. Assessment covers every region regardless.
- Acknowledge CAPABILITY_NAMED_IAM. The role name is fixed so that Firemind can derive the ARN without asking you for it.
- Set FaeTrustedAccountId to the Firemind account shown on the Quick Launch page, and FaeCallbackUrl to the registration endpoint shown there. Leave the remaining parameters at their defaults.
- On completion the stack reports the role back to Firemind automatically. If that call fails the stack rolls back, by design, so a silent half-configured state is not possible.
Trust
The trust policy is conditioned on an external ID equal to your own AWS account ID. Both sides derive it, so there is no secret to exchange and nothing to rotate.
Ending access
Delete the stack. That removes the role and every policy with it, and Firemind's access ends at that moment. No notice is required.
Support
Vendor support
For support, or questions about your assessment, contact Firemind at hello@firemind.com . We respond within one business day (UK business hours, Monday to Friday).
This assessment includes:
- Help setting up the read-only connection, including reviewing it with your security team before you run it
- An exposure assessment and a readout with a Firemind cloud architect
- Help removing Firemind's access when you are finished
There is no charge for this product and no paid support tier attached to it.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.