Tomcat ConnectorsWeb server / proxy · Apache
CVE-2024-46544
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect Default Permissions vulnerability in Apache Tomcat Connectors allows local users to view and modify shared memory containing mod_jk configuration which may lead to information disclosure and/or denial of service. This issue affects Apache Tomcat Connectors: from 1.2.9-beta through 1.2.49. Only mod_jk on Unix like systems is affected. Neither the ISAPI redirector nor mod_jk on Windows is affected. Users are recommended to upgrade to version 1.2.50, which fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIncorrect default permissions on shared memory in mod_jk (Apache Tomcat Connectors) allow local Unix users to read and modify the mod_jk configuration stored in shared memory, leading to information disclosure of sensitive configuration data or denial of service through corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Tomcat ConnectorsWeb server / proxy
>= 1.2.9, < 1.2.50
Debian LinuxOperating system
= 11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify mod_jk versionRun 'modjk_version' or check the mod_jk library version via 'httpd -M' (if loaded) or examine the mod_jk.so file version propertiesAffected if Installed version is 1.2.9 through 1.2.49 (inclusive)
-
Confirm mod_jk is in useCheck if the Apache HTTP Server is loading mod_jk by examining httpd.conf or running 'httpd -M | grep jk'Affected if mod_jk module is loaded and active
-
Verify shared memory configurationCheck if mod_jk worker properties enable shared memory caching (look for 'worker.*.shm' or 'JkShmSize' directives in httpd.conf or worker.properties)Affected if Shared memory is configured for mod_jk communication
-
Inspect shared memory permissionsRun 'ipcs -m' to list shared memory segments and check the 'perm' column for the mod_jk segment (typically labeled 'jk_')Affected if Permissions allow world read/write (e.g., 666) or group access beyond the web server user
You are affected if mod_jk version is between 1.2.9 and 1.2.49, shared memory is enabled, and the shared memory segment permissions are overly permissive to local users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.50
Upgrade Apache Tomcat Connectors to version 1.2.50 or later which fixes the overly permissive shared memory defaults.
1.2.50
- Identify the current version of mod_jk (tomcat-connectors) installed on the system
- Download Apache Tomcat Connectors version 1.2.50 from the official Apache archive (https://tomcat.apache.org/download-connectors.cgi) or your distribution's package repository
- Replace the existing mod_jk shared library and configuration files with the new version from 1.2.50
- Verify the permissions on the shared memory segments used by mod_jk are correctly set (should be restrictive, typically 0600 or similar)
- Restart Apache httpd to load the updated mod_jk module
- Verify the new version is loaded and the shared memory permissions are correct
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tomcat Connectors
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46544 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data