# CVE-2023-28708: Apache Tomcat: JSESSIONID Cookie missing secure attribute in some configurations > Attackers can intercept session cookies transmitted over insecure channels when using RemoteIpFilter with specific reverse proxy configurations. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Mar 2023 - **Updated:** 4 Nov 2025 - **Also known as:** BIT-tomcat-2023-28708, CLEANSTART-2026-RF65873, CLSA-2024-1735064733, CLSA-2024-1735065713, CLSA-2026-1793132890, DEBIAN-CVE-2023-28708, GHSA-2c9m-w27f-53rm, OESA-2023-1247, SUSE-SU-2023:1669-1, SUSE-SU-2023:1672-1, UBUNTU-CVE-2023-28708, openSUSE-SU-2024:12821-1 ## What is CVE-2023-28708? CVE-2023-28708 is a medium-severity vulnerability in Apache Tomcat, published on 22 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description When using the RemoteIpFilter with requests received from a reverse proxy via HTTP that include the X-Forwarded-Proto header set to https, session cookies created by Apache Tomcat 11.0.0-M1 to 11.0.0.-M2, 10.1.0-M1 to 10.1.5, 9.0.0-M1 to 9.0.71 and 8.5.0 to 8.5.85 did not include the secure attribute. This could result in the user agent transmitting the session cookie over an insecure channel. Older, EOL versions may also be affected. Weakness: CWE-523 (Unprotected Transport of Credentials) ## Which versions are affected by CVE-2023-28708? 9 open source packages ship an affected version, including org.apache.tomcat:tomcat-catalina and tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0-M1 | 10.1.6 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 10.1.0-M1 | 10.1.6 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 11.0.0-M1 | 11.0.0-M3 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 11.0.0-M1 | 11.0.0-M3 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.86 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.86 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0-M1 | 9.0.72 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0-M1 | 9.0.72 | | `tomcat` | Bitnami | From 8.5.0 | 8.5.86, 9.0.72, 10.1.6 | | `tomcat` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 9.0.36-150100.4.90.1 | | `tomcat` | SUSE:Linux Enterprise Server 12 SP4-ESPOS | All versions | 9.0.36-3.102.1 | | `tomcat` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 9.0.36-3.102.1 | | `tomcat` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 9.0.36-3.102.1 | | `tomcat` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 9.0.36-150100.4.90.1 | | `tomcat` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 9.0.36-3.102.1 | | `tomcat` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 9.0.36-3.102.1 | | `tomcat` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 9.0.36-150100.4.90.1 | | `tomcat` | SUSE:OpenStack Cloud 9 | All versions | 9.0.36-3.102.1 | | `tomcat` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 9.0.36-3.102.1 | | `tomcat` | openSUSE:Tumbleweed | All versions | 9.0.43-15.1 | Products: Apache Tomcat. ## How do I fix CVE-2023-28708? Upgrade org.apache.tomcat:tomcat-catalina to a fixed version for your release line: 10.1.6, 11.0.0-M3, 8.5.86 or 9.0.72. ## Is CVE-2023-28708 being exploited? There is no known exploitation of CVE-2023-28708 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-28708 and fix it if it is affected. What it is: CVE-2023-28708 is a medium-severity vulnerability in Apache Tomcat, published on 22 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2023-28708 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat:tomcat-catalina (Maven): affected from 10.1.0-M1; fixed in 10.1.6 - org.apache.tomcat:tomcat-catalina (Maven): affected from 10.1.0-M1; fixed in 10.1.6 - org.apache.tomcat:tomcat-catalina (Maven): affected from 11.0.0-M1; fixed in 11.0.0-M3 - org.apache.tomcat:tomcat-catalina (Maven): affected from 11.0.0-M1; fixed in 11.0.0-M3 - org.apache.tomcat:tomcat-catalina (Maven): affected from 8.5.0; fixed in 8.5.86 - org.apache.tomcat:tomcat-catalina (Maven): affected from 8.5.0; fixed in 8.5.86 - org.apache.tomcat:tomcat-catalina (Maven): affected from 9.0.0-M1; fixed in 9.0.72 - org.apache.tomcat:tomcat-catalina (Maven): affected from 9.0.0-M1; fixed in 9.0.72 - tomcat (Bitnami): affected from 8.5.0; fixed in 8.5.86, 9.0.72, 10.1.6 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-28708/ (Markdown: https://insights.sbomify.com/CVE-2023-28708/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-28708 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-28708 - OSV: https://osv.dev/vulnerability/CVE-2023-28708 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-28708/ Summaries are generated and may contain mistakes; the official description above is the record.