CVE-2014-3527 (GCVE-0-2014-3527)

Vulnerability from cvelistv5 – Published: 2017-05-25 17:00 – Updated: 2024-08-06 10:50
VLAI?
Summary
When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request. This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed. If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.
Severity ?
No CVSS data available.
CWE
  • Access Control Bypass
Assigner
References
Impacted products
Vendor Product Version
Pivotal Spring Security Affected: 3.1 to 3.2.4
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-06T10:50:16.372Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://pivotal.io/security/cve-2014-3527"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Spring Security",
          "vendor": "Pivotal",
          "versions": [
            {
              "status": "affected",
              "version": "3.1 to 3.2.4"
            }
          ]
        }
      ],
      "datePublic": "2014-08-17T00:00:00",
      "descriptions": [
        {
          "lang": "en",
          "value": "When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request. This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed. If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "Access Control Bypass",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-05-25T16:57:01",
        "orgId": "c550e75a-17ff-4988-97f0-544cde3820fe",
        "shortName": "dell"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://pivotal.io/security/cve-2014-3527"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security_alert@emc.com",
          "ID": "CVE-2014-3527",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Spring Security",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "3.1 to 3.2.4"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Pivotal"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request. This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed. If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Access Control Bypass"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://pivotal.io/security/cve-2014-3527",
              "refsource": "CONFIRM",
              "url": "https://pivotal.io/security/cve-2014-3527"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "c550e75a-17ff-4988-97f0-544cde3820fe",
    "assignerShortName": "dell",
    "cveId": "CVE-2014-3527",
    "datePublished": "2017-05-25T17:00:00",
    "dateReserved": "2014-05-14T00:00:00",
    "dateUpdated": "2024-08-06T10:50:16.372Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.1.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"717CECB8-01C6-41B1-810B-23CFDB6E7FC4\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.1.1:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"1FF656E2-CE4E-4E84-BA94-E20778B1A5DE\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.1.2:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"90AA303B-99C8-4BBB-A832-0C84413AF941\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.1.3:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"64819EA6-4D21-4A69-90E7-CAEE78301CAA\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.1.4:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"F1D779B3-A540-4358-BE2F-D50990BC9181\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.2.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"EFD426B7-885E-4C37-BA39-9877BB10685F\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.2.1:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"D32668E1-4839-474C-A97D-0A485BF3CE04\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.2.2:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"CF0DADB2-8D42-4592-9433-2941E3D57F95\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.2.3:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"C97588A1-B874-41F2-871E-BD3D5057FAC0\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:vmware:spring_security:3.2.4:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"00D3C6A3-4C51-4B2D-867A-A17B3AA39A19\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request. This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed. If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.\"}, {\"lang\": \"es\", \"value\": \"Cuando se utiliza la autenticaci\\u00f3n de tickets de Proxy CAS de Spring Security, versiones de la 3.1 a la 3.2.4, un servicio CAS malicioso permitir\\u00eda enga\\u00f1ar a otro servicio CAS para autenticar un ticket proxy que no estaba asociado. Esto es debido a que la autenticaci\\u00f3n ticket del proxy usa la informaci\\u00f3n de HttpServletRequest que es rellenada con informaci\\u00f3n no confiable de la solicitud HTTP. Esto significa que si hay restricciones de control de acceso en las que los servicios CAS pueden autenticarse entre s\\u00ed, esta restricci\\u00f3n puede ser evitada. Si los usuarios no est\\u00e1n usando tickets proxy CAS y no est\\u00e1n basando sus decisiones de control de acceso en servicios CAS, entonces no hay impacto para los usuarios.\"}]",
      "id": "CVE-2014-3527",
      "lastModified": "2024-11-21T02:08:18.343",
      "metrics": "{\"cvssMetricV30\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.0\", \"vectorString\": \"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\", \"baseScore\": 9.8, \"baseSeverity\": \"CRITICAL\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 3.9, \"impactScore\": 5.9}], \"cvssMetricV2\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"2.0\", \"vectorString\": \"AV:N/AC:L/Au:N/C:P/I:P/A:P\", \"baseScore\": 7.5, \"accessVector\": \"NETWORK\", \"accessComplexity\": \"LOW\", \"authentication\": \"NONE\", \"confidentialityImpact\": \"PARTIAL\", \"integrityImpact\": \"PARTIAL\", \"availabilityImpact\": \"PARTIAL\"}, \"baseSeverity\": \"HIGH\", \"exploitabilityScore\": 10.0, \"impactScore\": 6.4, \"acInsufInfo\": true, \"obtainAllPrivilege\": false, \"obtainUserPrivilege\": false, \"obtainOtherPrivilege\": false, \"userInteractionRequired\": false}]}",
      "published": "2017-05-25T17:29:00.257",
      "references": "[{\"url\": \"https://pivotal.io/security/cve-2014-3527\", \"source\": \"security_alert@emc.com\", \"tags\": [\"Vendor Advisory\"]}, {\"url\": \"https://pivotal.io/security/cve-2014-3527\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Vendor Advisory\"]}]",
      "sourceIdentifier": "security_alert@emc.com",
      "vulnStatus": "Modified",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-287\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2014-3527\",\"sourceIdentifier\":\"security_alert@emc.com\",\"published\":\"2017-05-25T17:29:00.257\",\"lastModified\":\"2025-04-20T01:37:25.860\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service into authenticating a proxy ticket that was not associated. This is due to the fact that the proxy ticket authentication uses the information from the HttpServletRequest which is populated based upon untrusted information within the HTTP request. This means if there are access control restrictions on which CAS services can authenticate to one another, those restrictions can be bypassed. If users are not using CAS Proxy tickets and not basing access control decisions based upon the CAS Service, then there is no impact to users.\"},{\"lang\":\"es\",\"value\":\"Cuando se utiliza la autenticaci\u00f3n de tickets de Proxy CAS de Spring Security, versiones de la 3.1 a la 3.2.4, un servicio CAS malicioso permitir\u00eda enga\u00f1ar a otro servicio CAS para autenticar un ticket proxy que no estaba asociado. Esto es debido a que la autenticaci\u00f3n ticket del proxy usa la informaci\u00f3n de HttpServletRequest que es rellenada con informaci\u00f3n no confiable de la solicitud HTTP. Esto significa que si hay restricciones de control de acceso en las que los servicios CAS pueden autenticarse entre s\u00ed, esta restricci\u00f3n puede ser evitada. Si los usuarios no est\u00e1n usando tickets proxy CAS y no est\u00e1n basando sus decisiones de control de acceso en servicios CAS, entonces no hay impacto para los usuarios.\"}],\"metrics\":{\"cvssMetricV30\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.0\",\"vectorString\":\"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":9.8,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:L/Au:N/C:P/I:P/A:P\",\"baseScore\":7.5,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"LOW\",\"authentication\":\"NONE\",\"confidentialityImpact\":\"PARTIAL\",\"integrityImpact\":\"PARTIAL\",\"availabilityImpact\":\"PARTIAL\"},\"baseSeverity\":\"HIGH\",\"exploitabilityScore\":10.0,\"impactScore\":6.4,\"acInsufInfo\":true,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-287\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.1.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"717CECB8-01C6-41B1-810B-23CFDB6E7FC4\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.1.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"1FF656E2-CE4E-4E84-BA94-E20778B1A5DE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.1.2:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"90AA303B-99C8-4BBB-A832-0C84413AF941\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.1.3:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"64819EA6-4D21-4A69-90E7-CAEE78301CAA\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.1.4:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"F1D779B3-A540-4358-BE2F-D50990BC9181\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.2.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"EFD426B7-885E-4C37-BA39-9877BB10685F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.2.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"D32668E1-4839-474C-A97D-0A485BF3CE04\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.2.2:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"CF0DADB2-8D42-4592-9433-2941E3D57F95\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.2.3:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"C97588A1-B874-41F2-871E-BD3D5057FAC0\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:vmware:spring_security:3.2.4:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"00D3C6A3-4C51-4B2D-867A-A17B3AA39A19\"}]}]}],\"references\":[{\"url\":\"https://pivotal.io/security/cve-2014-3527\",\"source\":\"security_alert@emc.com\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://pivotal.io/security/cve-2014-3527\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Vendor Advisory\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.