{
  "@id": "urn:uuid:34e9f9e0-5a9b-492b-a49a-55ca47b1ed96",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-10-26T21:23:36.036761+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.springframework.social/spring-social-twitter@1.1.2.RELEASE-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.springframework.social/spring-social-twitter@1.1.2.RELEASE-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-10-26T21:23:36.036761+00:00",
      "status_notes": "Vulnerability CVE-2015-5258 is a false positive for org.springframework.social:spring-social-twitter 1.1.2.RELEASE-tuxcare.1. CVE-2015-5258 is a cross-site request forgery flaw in Spring Social Core, in the OAuth 2 authorization flow of its web connection support: the callback request was accepted without a state parameter, so an attacker could have a victim's browser complete an authorization the attacker started with their own provider account. The Spring advisory lists only Spring Social Core 1.0.0 to 1.0.3 and 1.1.0 to 1.1.2 as affected; Spring Social 1.1.3 fixes it by requiring the state parameter on the callback. Spring Social Twitter is a separate provider library that depends on spring-social-core and spring-social-config. Its sources contain only the Twitter API binding, connection factory, service provider and configuration classes under org.springframework.social.twitter; no released version of it contains a connect or sign-in controller or any OAuth 2 callback handling. The vulnerable code belongs to Spring Social Core and reaches applications only through that dependency.",
      "vulnerability": {
        "name": "CVE-2015-5258"
      },
      "impact_statement": "CVE-2015-5258 is a cross-site request forgery flaw in Spring Social Core, in the OAuth 2 authorization flow of its web connection support: the callback request was accepted without a state parameter, so an attacker could have a victim's browser complete an authorization the attacker started with their own provider account. The Spring advisory lists only Spring Social Core 1.0.0 to 1.0.3 and 1.1.0 to 1.1.2 as affected; Spring Social 1.1.3 fixes it by requiring the state parameter on the callback. Spring Social Twitter is a separate provider library that depends on spring-social-core and spring-social-config. Its sources contain only the Twitter API binding, connection factory, service provider and configuration classes under org.springframework.social.twitter; no released version of it contains a connect or sign-in controller or any OAuth 2 callback handling. The vulnerable code belongs to Spring Social Core and reaches applications only through that dependency."
    }
  ]
}