CERTA-2011-AVI-404

Vulnerability from certfr_avis - Published: - Updated:

Deux vulnérabilités dans les produits Cisco SA 500 Series Security Appliances permettent à une personne malintentionnée soit d'élever ses privilèges, soit de porter atteinte à la confidentialité des données.

Description

Deux vulnérabilités dans les produits Cisco SA 500 Series Security Appliances ont été découvertes :

  • la première permet à une personne distante non authentifiée de porter atteinte à la confidentialité des données d'identification via une injection de code SQL (CVE-2011-2546) ;
  • la seconde permet à un utilisateur authentifié d'élever ses privilèges sur le système par l'envoi de paramètres spécifiques via des formulaires web (CVE-2011-2547).

Solution

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
Cisco N/A Cisco SA520 ;
Cisco N/A Cisco SA520W ;
Cisco N/A Cisco SA540.

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Cisco SA520 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Cisco",
          "scada": false
        }
      }
    },
    {
      "description": "Cisco SA520W ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Cisco",
          "scada": false
        }
      }
    },
    {
      "description": "Cisco SA540.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Cisco",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s dans les produits Cisco SA 500 Series Security\nAppliances ont \u00e9t\u00e9 d\u00e9couvertes :\n\n-   la premi\u00e8re permet \u00e0 une personne distante non authentifi\u00e9e de\n    porter atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es d\u0027identification\n    via une injection de code SQL (CVE-2011-2546) ;\n-   la seconde permet \u00e0 un utilisateur authentifi\u00e9 d\u0027\u00e9lever ses\n    privil\u00e8ges sur le syst\u00e8me par l\u0027envoi de param\u00e8tres sp\u00e9cifiques via\n    des formulaires web (CVE-2011-2547).\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2011-2546",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-2546"
    },
    {
      "name": "CVE-2011-2547",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-2547"
    }
  ],
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Cisco 20110720-sa500 du 20 juillet    2011 :",
      "url": "http://www.cisco.com/warp/public/707/cisco-sa-20110720-sa500.shtml"
    }
  ],
  "reference": "CERTA-2011-AVI-404",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-07-21T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    },
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": "Deux vuln\u00e9rabilit\u00e9s dans les produits Cisco SA 500 Series Security\nAppliances permettent \u00e0 une personne malintentionn\u00e9e soit d\u0027\u00e9lever ses\nprivil\u00e8ges, soit de porter atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es.\n",
  "title": "Vuln\u00e9rabilit\u00e9s dans les produits Cisco SA 500 Series Security Appliances",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Cisco 20110720-sa500 du 20 juillet 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.