# CVE-2017-7674: Insufficient Verification of Data Authenticity in Apache Tomcat > Missing Vary header in CORS filter allows cache poisoning, potentially exposing sensitive data to unauthorized users. - **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:** 11 Aug 2017 - **Updated:** 15 Oct 2026 - **Also known as:** DSA-3974-1, GHSA-73rx-3f9r-x949, UBUNTU-CVE-2017-7674 ## What is CVE-2017-7674? CVE-2017-7674 is a medium-severity vulnerability in Apache Tomcat, published on 11 Aug 2017. 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 The CORS Filter in Apache Tomcat 9.0.0.M1 to 9.0.0.M21, 8.5.0 to 8.5.15, 8.0.0.RC1 to 8.0.44 and 7.0.41 to 7.0.78 did not add an HTTP Vary header indicating that the response varies depending on Origin. This permitted client and server side cache poisoning in some circumstances. Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2017-7674? 8 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat` | Maven | From 7.0.41 | 7.0.79 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.41 | 7.0.79 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0.RC1 | 8.0.45 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0.RC1 | 8.0.45 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.16 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.16 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M22 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M22 | Products: Apache Tomcat. ## How do I fix CVE-2017-7674? Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 7.0.79, 8.0.45, 8.5.16 or 9.0.0.M22. ## Is CVE-2017-7674 being exploited? There is no known exploitation of CVE-2017-7674 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-2017-7674 and fix it if it is affected. What it is: CVE-2017-7674 is a medium-severity vulnerability in Apache Tomcat, published on 11 Aug 2017. 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-2017-7674 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 7.0.41; fixed in 7.0.79 - org.apache.tomcat:tomcat (Maven): affected from 7.0.41; fixed in 7.0.79 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0.RC1; fixed in 8.0.45 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0.RC1; fixed in 8.0.45 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.16 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.16 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M22 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M22 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-2017-7674/ (Markdown: https://insights.sbomify.com/CVE-2017-7674/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7674 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7674 - OSV: https://osv.dev/vulnerability/CVE-2017-7674 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7674/ Summaries are generated and may contain mistakes; the official description above is the record.