fkie_cve-2008-7310
Vulnerability from fkie_nvd
Published
2012-04-05 13:25
Modified
2025-04-11 00:51
Severity ?
Summary
Spree 0.2.0 does not properly restrict the use of a hash to provide values for a model's attributes, which allows remote attackers to set the Order state value and bypass the intended payment step via a modified URL, related to a "mass assignment" vulnerability.
References
cve@mitre.orghttp://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignment
cve@mitre.orghttp://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-params/Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignment
af854a3a-2127-422b-91ae-364da2661108http://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-params/Vendor Advisory
Impacted products
Vendor Product Version
spreecommerce spree 0.2.0


To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:spreecommerce:spree:0.2.0:*:*:*:*:*:*:*",
              "matchCriteriaId": "4B5EABA0-0D43-4240-B080-80BB7015074F",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Spree 0.2.0 does not properly restrict the use of a hash to provide values for a model\u0027s attributes, which allows remote attackers to set the Order state value and bypass the intended payment step via a modified URL, related to a \"mass assignment\" vulnerability."
    },
    {
      "lang": "es",
      "value": "Spree v0.2.0 no restringe adecuadamente el uso de un hash para proporcionar los valores de los atributos de un modelo, lo que permite a atacantes remotos establecer el valor de estado de orden (Order State Value) y evitar el paso del pago solicitado a trav\u00e9s de una URL modificada, est\u00e1 relacionado con una vulnerabilidad de \"asignaci\u00f3n masiva\"."
    }
  ],
  "id": "CVE-2008-7310",
  "lastModified": "2025-04-11T00:51:21.963",
  "metrics": {
    "cvssMetricV2": [
      {
        "acInsufInfo": false,
        "baseSeverity": "MEDIUM",
        "cvssData": {
          "accessComplexity": "LOW",
          "accessVector": "NETWORK",
          "authentication": "NONE",
          "availabilityImpact": "NONE",
          "baseScore": 5.0,
          "confidentialityImpact": "NONE",
          "integrityImpact": "PARTIAL",
          "vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
          "version": "2.0"
        },
        "exploitabilityScore": 10.0,
        "impactScore": 2.9,
        "obtainAllPrivilege": false,
        "obtainOtherPrivilege": false,
        "obtainUserPrivilege": false,
        "source": "nvd@nist.gov",
        "type": "Primary",
        "userInteractionRequired": false
      }
    ]
  },
  "published": "2012-04-05T13:25:21.177",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignment"
    },
    {
      "source": "cve@mitre.org",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "http://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-params/"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignment"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "http://spreecommerce.com/blog/2008/09/16/security-vulnerability-mass-assignment-of-order-params/"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-255"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}


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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.