Listing Thumbnail

    Java Vulnerability Assessment and Remediation on AWS by Firemind

     Info
    Sold by: Firemind 
    Find every Java runtime in your AWS estate, fix it, and keep it fixed. EC2, container images, ECS, EKS, Fargate, Lambda and Elastic Beanstalk are inventoried, updated or mitigated under your change rules, with the running build verified, then monitored so new deployments don't bring an exposed version back.

    Overview

    Overview: When a critical flaw lands in the Java runtime itself, every Java application on it is exposed. The first question is where Java runs in your estate. Built on Firemind's IT Operations Engine, this service answers it from your AWS accounts and repositories, fixes what can be fixed, verifies the build running, and keeps the exposure closed.

    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.

    Where Java hides on AWS

    • Amazon EC2 servers running Java from operating-system packages or an application's own JDK
    • Container images in Amazon ECR on Amazon ECS, Amazon EKS and AWS Fargate, each carrying the JDK it was built with
    • AWS Lambda functions on Java runtimes or container images, and Elastic Beanstalk Java environments
    • Products and Marketplace appliances that bundle their own runtime, such as identity providers and build servers

    What you receive

    • Find. An inventory of every Java runtime in scope, with vendor, build, exposure and fix status, built from EC2 instance metadata, AWS Systems Manager Inventory, Amazon Inspector findings, image metadata and your repositories. Images are inspected from the inside with access you grant during onboarding. Each workload is checked against its processor: AVX-512 VBMI instance types first, Graviton confirmed clear, resize risk flagged.
    • Fix. Runtime updates through AWS Systems Manager Patch Manager with the restarts they need, JDK and base-image pull requests your engineers review, image rebuilds through your pipelines, and Lambda runtime updates. Where an update has to wait, interim JVM flags are applied. The build actually running is verified after each fix, and secrets the affected processes could see are rotated where you choose.
    • Keep green. Continuous checks that new instances, images and functions ship fixed builds, that build files stay current, that interim flags come off once fixed, and that instance changes don't move an unpatched workload onto an affected chip.

    What stays out of scope

    Products and appliances that bundle their own Java are found and tracked against the vendor's fixed release, and applying it is scoped with you. Moving off an out-of-support Java line is an upgrade, scoped with you and raised as pull requests. Builds with no fix yet are mitigated until it ships.

    How it works

    1. Connect. After the private offer is accepted, you deploy an IAM role using AWS CloudFormation and connect your source control. A full description of the role and its policy statements is provided before deployment. The Engine works through the AWS API under temporary credentials, and every action is recorded in your own AWS CloudTrail.
    2. Scan. The first exposure report is ready within days of connection.
    3. Heal. Fixes run inside your change rules. Low-risk, reversible changes run automatically. Higher-risk changes, such as restarting or redeploying production services, wait for a named approver.
    4. Monitor. Keep-green checks run continuously for the term you choose.

    Deployment: Pilot scopes run from Firemind's AWS environment. In production the Engine runs inside your own AWS accounts. Running the Engine in your accounts may incur AWS infrastructure charges, for example Amazon Bedrock and compute. These are billed separately from this AWS Marketplace transaction and are your responsibility.

    Pricing: Delivered through an AWS Marketplace private offer, scoped to your estate. Assessment, remediation and keep-green monitoring can be contracted together or separately. Contact hello@firemind.com  to scope.

    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 Java wherever it runs on AWS, including the copies OS patching misses: bundled JDKs in container images, Lambda container images, vendor products and Marketplace appliances, each checked against its processor.
    • Fixes under your rules: runtime updates, image rebuilds, base-image pull requests, interim JVM-flag mitigations and secret rotation, with high-risk changes held for a named approver and every action in your CloudTrail.
    • Keeps it green: continuous checks stop new instances, images, functions and instance-type changes from bringing an exposed Java build back.

    Details

    Sold by

    Delivery method

    Deployed on AWS

    Pricing

    Custom pricing options

    Pricing is based on your specific requirements and eligibility. To get a custom quote for your needs, request a private offer.

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Support

    Vendor support

    For support or to scope a pilot, contact Firemind at hello@firemind.com . We respond within one business day (UK business hours, Monday to Friday). Active IT Operations Engine engagements include: defined response SLAs by severity; a dedicated Slack or Microsoft Teams channel with your engagement team; weekly status reviews and quarterly business reviews; a named engagement lead and technical owner; and 24/7 monitoring of agent actions with documented engineer escalation paths agreed during onboarding. Website:

    Software associated with this service