CERTA-2011-AVI-083

Vulnerability from certfr_avis - Published: 2011-02-10 - Updated: 2011-02-10

Plusieurs vulnérabilités présentes dans Ruby on Rails permettent à un utilisateur distant de contourner la politique de sécurité, de porter atteinte à l'intégrité de données et de conduire des attaques de type injection de code indirecte à distance.

Description

Quatres vulnérabilités ont été identifiées dans Ruby on Rails.

La première et la deuxième, présentes dans les versions de la branche 2 et de la branche 3 de Ruby on Rails, permettent à un utilisateur de conduire des attaques de type injection de code indirecte à distance (CVE-2011-446 et CVE-2011-447).

La troisième et la quatrième, ne touchant que les versions de la branche 3, permettent à un utilisateur distant malintentionné de contourner certains filtrages du système (CVE-2011-448) et de réaliser des attaques de type injection SQL (CVE-2011-449).

Solution

Se référer à la note de sortie de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
Ruby on Rails Ruby on Rails Ruby on Rails versions 2.3.10 et antérieures (CVE-2011-0446 à CVE-2011-0449) ;
Ruby on Rails Ruby on Rails Ruby on Rails versions 3.0.3 et antérieures (CVE-2011-0448 et CVE-2011-0449 uniquement).

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Ruby on Rails versions 2.3.10 et ant\u00e9rieures (CVE-2011-0446 \u00e0 CVE-2011-0449) ;",
      "product": {
        "name": "Ruby on Rails",
        "vendor": {
          "name": "Ruby on Rails",
          "scada": false
        }
      }
    },
    {
      "description": "Ruby on Rails versions 3.0.3 et ant\u00e9rieures (CVE-2011-0448 et CVE-2011-0449 uniquement).",
      "product": {
        "name": "Ruby on Rails",
        "vendor": {
          "name": "Ruby on Rails",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nQuatres vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans Ruby on Rails.\n\nLa premi\u00e8re et la deuxi\u00e8me, pr\u00e9sentes dans les versions de la branche 2\net de la branche 3 de Ruby on Rails, permettent \u00e0 un utilisateur de\nconduire des attaques de type injection de code indirecte \u00e0 distance\n(CVE-2011-446 et CVE-2011-447).\n\nLa troisi\u00e8me et la quatri\u00e8me, ne touchant que les versions de la branche\n3, permettent \u00e0 un utilisateur distant malintentionn\u00e9 de contourner\ncertains filtrages du syst\u00e8me (CVE-2011-448) et de r\u00e9aliser des attaques\nde type injection SQL (CVE-2011-449).\n\n## Solution\n\nSe r\u00e9f\u00e9rer \u00e0 la note de sortie de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2011-0447",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-0447"
    },
    {
      "name": "CVE-2011-0449",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-0449"
    },
    {
      "name": "CVE-2011-0448",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-0448"
    },
    {
      "name": "CVE-2011-0446",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-0446"
    }
  ],
  "initial_release_date": "2011-02-10T00:00:00",
  "last_revision_date": "2011-02-10T00:00:00",
  "links": [
    {
      "title": "Note de sortie des versions 2.3.11 et 3.0.4 de Ruby on    Rails du 08 f\u00e9vrier 2011 :",
      "url": "http://weblog.rubyonrails.org/2011/2/8/new-releases-2-3-11-and-3-0-4"
    }
  ],
  "reference": "CERTA-2011-AVI-083",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-02-10T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "Injection de code indirecte \u00e0 distance"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans Ruby on Rails permettent \u00e0 un\nutilisateur distant de contourner la politique de s\u00e9curit\u00e9, de porter\natteinte \u00e0 l\u0027int\u00e9grit\u00e9 de donn\u00e9es et de conduire des attaques de type\ninjection de code indirecte \u00e0 distance.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Ruby on Rails",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Note de sortie des versions 2.3.11 et 3.0.4 de Ruby on Rails du 08 f\u00e9vrier 2011",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.