{ "@id": "urn:uuid:79612018-951a-433a-96a9-c78cb16bdfb6", "role": "Document Creator", "author": "https://tuxcare.com", "version": 35, "@context": "https://openvex.dev/ns/v0.2.0", "timestamp": "2026-11-10T15:51:00.040518+00:00", "statements": [ { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-30T12:33:04.556385+00:00", "status_notes": "Vulnerability CVE-2009-1190 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. not_affected \u2014 Spring Framework 4.2.9.RELEASE is not affected by CVE-2009-1190. While the framework still contains deserialization code (HttpInvokerServiceExporter) with no Spring-level filtering for Pattern objects, the vulnerability requires JDK < 1.6 to exploit. Spring 4.2.9 is compiled with Java 6 bytecode compatibility (sourceCompatibility = 1.6) and cannot run on Java 5 or earlier. The JDK 6+ runtime in...", "vulnerability": { "name": "CVE-2009-1190" }, "impact_statement": "not_affected \u2014 Spring Framework 4.2.9.RELEASE is not affected by CVE-2009-1190. While the framework still contains deserialization code (HttpInvokerServiceExporter) with no Spring-level filtering for Pattern objects, the vulnerability requires JDK < 1.6 to exploit. Spring 4.2.9 is compiled with Java 6 bytecode compatibility (sourceCompatibility = 1.6) and cannot run on Java 5 or earlier. The JDK 6+ runtime in..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-06T17:35:21.880444+00:00", "status_notes": "Vulnerability CVE-2011-2730 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 4.2.9.RELEASE is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6).", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2011-2730" }, "impact_statement": "Prechecker: No vulnerable code from the fix was found, and the functions the fix changes were not found in this version. Version 4.2.9.RELEASE is on a newer release line than any version the advisories list as affected. Advisories: GitHub GHSA-wv88-pf73-x22p (affected up to 3.0.6), NVD (affected up to 3.0.5), Snyk (affected up to 3.0.6)." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-03T09:43:37.074687+00:00", "status_notes": "Vulnerability CVE-2011-2894 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. not_affected \u2014 The target Spring Framework 4.2.9.RELEASE contains the complete fix for CVE-2011-2894. The acceptProxyClasses defense mechanism was added by upstream Spring maintainer Juergen Hoeller in commit 7d8aa05c and shipped with the upstream 4.2.9.RELEASE before TuxCare onboarded this version. The defense code includes: (1) acceptProxyClasses field in ConfigurableObjectInputStream, (2) validation in res...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2011-2894" }, "impact_statement": "not_affected \u2014 The target Spring Framework 4.2.9.RELEASE contains the complete fix for CVE-2011-2894. The acceptProxyClasses defense mechanism was added by upstream Spring maintainer Juergen Hoeller in commit 7d8aa05c and shipped with the upstream 4.2.9.RELEASE before TuxCare onboarded this version. The defense code includes: (1) acceptProxyClasses field in ConfigurableObjectInputStream, (2) validation in res..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-02T17:10:00.096270+00:00", "status_notes": "Vulnerability CVE-2014-3578 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 4.2.9.RELEASE-tuxcare.13. The vulnerable code pattern was fixed in upstream release 4.2.9.RELEASE, which already contained the defense code when TuxCare onboarded this version. The fix (checking if prefix contains \"/\" and discarding it) is present at StringUtils.java lines 631-636, introduced by upstream commit 8...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2014-3578" }, "impact_statement": "not_affected \u2014 CVE-2014-3578 directory traversal vulnerability is NOT present in Spring Framework 4.2.9.RELEASE-tuxcare.13. The vulnerable code pattern was fixed in upstream release 4.2.9.RELEASE, which already contained the defense code when TuxCare onboarded this version. The fix (checking if prefix contains \"/\" and discarding it) is present at StringUtils.java lines 631-636, introduced by upstream commit 8..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-03T19:13:22.019052+00:00", "status_notes": "Vulnerability CVE-2015-0201 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5, where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (SecureRandom for initial seed, then java.util.Random). The fix switched to JdkIdGenerator using UUID.randomUUID() (cryptographically secure). Target version 4.2.9.RELEASE already contains this upstream fix from January 2015, shipped in the up...", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2015-0201" }, "impact_statement": "not_affected \u2014 CVE-2015-0201 affects Spring Framework 4.1.x before 4.1.5, where the Java SockJS client generated predictable session IDs using AlternativeJdkIdGenerator (SecureRandom for initial seed, then java.util.Random). The fix switched to JdkIdGenerator using UUID.randomUUID() (cryptographically secure). Target version 4.2.9.RELEASE already contains this upstream fix from January 2015, shipped in the up..." }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-03T13:02:11.032230+00:00", "status_notes": "Vulnerability CVE-2015-5211 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. Target version 4.2.9.RELEASE is NOT vulnerable to CVE-2015-5211 (Reflected File Download). The complete RFD defense was shipped in upstream Spring Framework 4.2.2 (October 2015) and is present in this target. The defense adds a Content-Disposition header with a safe filename when the request URL contains an extension not in the whitelist, preventing the browser from downloading/executing responses with attacker-controlled malicious extensions (.bat, .cmd, .sh, etc.). Fix authored by Spring team (@pivotal.io), included in the upstream release that TuxCare onboarded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0).", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2015-5211" }, "impact_statement": "Target version 4.2.9.RELEASE is NOT vulnerable to CVE-2015-5211 (Reflected File Download). The complete RFD defense was shipped in upstream Spring Framework 4.2.2 (October 2015) and is present in this target. The defense adds a Content-Disposition header with a safe filename when the request URL contains an extension not in the whitelist, preventing the browser from downloading/executing responses with attacker-controlled malicious extensions (.bat, .cmd, .sh, etc.). Fix authored by Spring team (@pivotal.io), included in the upstream release that TuxCare onboarded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.2.0, < 4.2.2; >= 4.0.0, < 4.1.8; < 3.2.15), NVD (= 3.2.0; = 3.2.1; = 3.2.2; = 3.2.3; = 3.2.4; = 3.2.5; = 3.2.6; = 3.2.7; = 3.2.8; = 3.2.9; = 3.2.10; = 3.2.11; = 3.2.12; = 3.2.13; = 3.2.14; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.1.0; = 4.1.1; = 4.1.2; = 4.1.3; = 4.1.4; = 4.1.5; = 4.1.6; = 4.1.7; = 4.2.0; = 4.2.1), Snyk (>= 3.2.0.RELEASE, < 3.2.15.RELEASE; >= 4.0.0.RELEASE, < 4.1.8.RELEASE; >= 4.2.0.RELEASE, < 4.2.2.RELEASE; <= 0; <= 0)." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2016-5007 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2016-5007" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-05T17:08:00.052883+00:00", "status_notes": "Vulnerability CVE-2018-11040 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core, and is fixed in 4.2.9.RELEASE-tuxcare.14.", "vulnerability": { "name": "CVE-2018-11040" }, "action_statement": "Vulnerability CVE-2018-11040 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core, and is fixed in 4.2.9.RELEASE-tuxcare.14." }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-29T00:51:30.888148+00:00", "status_notes": "Vulnerability CVE-2018-1199 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2018-1199" }, "action_statement": "Vulnerability CVE-2018-1199 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2018-1257 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2018-1257" } }, { "status": "not_affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-11-09T20:55:27.082072+00:00", "status_notes": "Vulnerability CVE-2018-1258 does not affect version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core. Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. The AOP fix removes the condition that substitutes null for JDK proxy target classes, allowing their methods to be resolved (`patches/03-8b051ab06ef6.patch:74`). HEAD already passes `targetClass` directly to method resolution and then resolves bridge methods, so that vulnerable proxy-exclusion behavior is absent (AopUtils.java:164). The underlying resolver looks up public methods through `targetClass.getMethod`, preserving resolution against the supplied class (ClassUtils.java:763). During ordinary JDK-proxy invocation, that class comes from the actual target object, permitting implementation-method lookup (JdkDynamicAopProxy.java:187).", "justification": "vulnerable_code_not_present", "vulnerability": { "name": "CVE-2018-1258" }, "impact_statement": "Re-checked 2026-11-10 by the vulnerability checker and confirmed by an independent code review: not affected. The AOP fix removes the condition that substitutes null for JDK proxy target classes, allowing their methods to be resolved (`patches/03-8b051ab06ef6.patch:74`). HEAD already passes `targetClass` directly to method resolution and then resolves bridge methods, so that vulnerable proxy-exclusion behavior is absent (AopUtils.java:164). The underlying resolver looks up public methods through `targetClass.getMethod`, preserving resolution against the supplied class (ClassUtils.java:763). During ordinary JDK-proxy invocation, that class comes from the actual target object, permitting implementation-method lookup (JdkDynamicAopProxy.java:187)." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2018-1271 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2018-1271" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2018-1272 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2018-1272" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2018-15756 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2018-15756" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-28T22:44:11.275398+00:00", "status_notes": "Vulnerability CVE-2021-22060 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2021-22060" }, "action_statement": "Vulnerability CVE-2021-22060 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2021-22096 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2021-22096" } }, { "status": "affected", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-29T03:48:46.502543+00:00", "status_notes": "Vulnerability CVE-2024-22233 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2024-22233" }, "action_statement": "Vulnerability CVE-2024-22233 affects version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core." }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2025-41249 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2025-41249" } }, { "status": "fixed", "products": [ { "@id": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13", "identifiers": { "purl": "pkg:maven/org.springframework/spring-core@4.2.9.RELEASE-tuxcare.13" } } ], "timestamp": "2026-10-21T17:02:44.816066+00:00", "status_notes": "Vulnerability CVE-2026-41848 is fixed in version 4.2.9.RELEASE-tuxcare.13 of org.springframework:spring-core.", "vulnerability": { "name": "CVE-2026-41848" } } ] }