How severe is CVE-2017-7674?

CVE-2017-7674 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-7674?

CVE-2017-7674 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-7674?

Update org.apache.tomcat:tomcat to 9.0.0.M22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7674 is resolved across your whole dependency graph.

How do I detect CVE-2017-7674 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2017-7674 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2017-7674?

O3 pinpoints whether CVE-2017-7674 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2017-7674 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-7674 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2017-7674?

CVE-2017-7674 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-7674 published, and has it been updated?

CVE-2017-7674 was published on August 11, 2017 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2017-7674

MEDIUM

CVE-2017-7674 is a medium-severity (CVSS 4.3) CWE-345 vulnerability in org.apache.tomcat:tomcat. O3 Security confirms whether CVE-2017-7674 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Insufficient Verification of Data Authenticity in Apache Tomcat

Also known asGHSA-73rx-3f9r-x949

Published

Aug 11, 2017

Updated

Jul 8, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M1&&< 9.0.0.M22	9.0.0.M22
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.0&&< 8.5.16	8.5.16
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0.RC1&&< 8.0.45	8.0.45
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.41&&< 7.0.79	7.0.79

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.tomcat:tomcat to 9.0.0.M22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7674 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2017-7674 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-7674. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-7674 in your dependencies?

O3 detects CVE-2017-7674 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works