Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Use of Hard-coded Cryptographic Key in Apache Tomcat

CVE-2011-5064GHSA-6cr4-7c7p-p3xv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.tomcat:tomcat 7.0.12, 6.0.33, 5.5.34), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.apache.tomcat:tomcat

    Affected
    >= 5.5.0, < 5.5.34>= 6.0.0, < 6.0.33>= 7.0.0, < 7.0.12
    Fixed in
    7.0.12, 6.0.33, 5.5.34

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2011-5064: 6.33% estimated exploitation activity in the next 30 days; percentile 93.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

DigestAuthenticator.java in the HTTP Digest Access Authentication implementation in Apache Tomcat 5.5.x before 5.5.34, 6.x before 6.0.33, and 7.x before 7.0.12 uses Catalina as the hard-coded server secret (aka private key), which makes it easier for remote attackers to bypass cryptographic protection mechanisms by leveraging knowledge of this string, a different vulnerability than CVE-2011-1184.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6cr4-7c7p-p3xv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2011-5064

Advisory: Use of Hard-coded Cryptographic Key in Apache Tomcat
IDs: CVE-2011-5064, GHSA-6cr4-7c7p-p3xv
Record: https://patchnext.com/advisories/cve-2011-5064 (revision 1, source checked 26 Oct 2026, 16:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.tomcat:tomcat 7.0.12, 6.0.33, 5.5.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.tomcat:tomcat: affected >= 5.5.0, < 5.5.34; >= 6.0.0, < 6.0.33; >= 7.0.0, < 7.0.12; fixed in 7.0.12, 6.0.33, 5.5.34

## Suggested inspection (read-only)
- Maven org.apache.tomcat:tomcat: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.tomcat:tomcat.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6cr4-7c7p-p3xv (GitHub-reviewed advisory GHSA-6cr4-7c7p-p3xv lists affected ranges: Maven org.apache.tomcat:tomcat >=5.5.0 =6.0.0 =7.0.0 <7.0.12)

Commands are suggestions: review each one before running it.

Loading voting…