CERTA-2012-AVI-225

Vulnerability from certfr_avis - Published: - Updated:

De multiples vulnérabilités ont été corrigées dans le module Apache de HP-UX. Elles permettent à un utilisateur malintentionné de porter atteinte à la confidentialité des données, causer un déni de service et d'élever ses privilèges. La liste ci-dessous fournit le détail de ces vulnérabilités :

  • CVE-2011-3607 : la fonction api_pregsub, lorsque le module mod_setenvif est activé, est vulnérable à un dépassement d'entier permettant à un utilisateur malintentionné d'élever ses privilèges ;
  • CVE-2012-0021 : mod_log_config ne gère pas correctement certains cookies, ce qui peut conduire à un arrêt inopiné du service Apache ;
  • CVE-2012-0031 : un problème dans la gestion des segments de mémoire partagée peut conduire à un déni de service local ;
  • CVE-2012-0053 : lorsqu'aucune page personnalisée n'est définie pour le code d'erreur 400, il est possible d'obtenir les cookies httpOnly.

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
N/A N/A HP-UX B.11.31 ;
N/A N/A HP-UX B.11.23 ;
N/A N/A HP-UX B.11.11.

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "HP-UX B.11.31 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    },
    {
      "description": "HP-UX B.11.23 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    },
    {
      "description": "HP-UX B.11.11.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## 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-2012-0053",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0053"
    },
    {
      "name": "CVE-2012-0021",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0021"
    },
    {
      "name": "CVE-2012-0031",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0031"
    },
    {
      "name": "CVE-2011-3607",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-3607"
    }
  ],
  "links": [
    {
      "title": "Document du CERTA CERTA-2012-AVI-050 du 02 f\u00e9vrier 2012 :",
      "url": "http://www.certa.ssi.gouv.fr/site/CERTA-2012-AVI-050/index.html"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 HP c03278391 du 18 avril 2012 :",
      "url": "http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03278391"
    }
  ],
  "reference": "CERTA-2012-AVI-225",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2012-04-20T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
    },
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans le module \u003cspan\nclass=\"textit\"\u003eApache\u003c/span\u003e de \u003cspan class=\"textit\"\u003eHP-UX\u003c/span\u003e. Elles\npermettent \u00e0 un utilisateur malintentionn\u00e9 de porter atteinte \u00e0 la\nconfidentialit\u00e9 des donn\u00e9es, causer un d\u00e9ni de service et d\u0027\u00e9lever ses\nprivil\u00e8ges. La liste ci-dessous fournit le d\u00e9tail de ces vuln\u00e9rabilit\u00e9s\n:\n\n-   CVE-2011-3607 : la fonction \u003cspan class=\"textit\"\u003eapi_pregsub\u003c/span\u003e,\n    lorsque le module \u003cspan class=\"textit\"\u003emod_setenvif\u003c/span\u003e est\n    activ\u00e9, est vuln\u00e9rable \u00e0 un d\u00e9passement d\u0027entier permettant \u00e0 un\n    utilisateur malintentionn\u00e9 d\u0027\u00e9lever ses privil\u00e8ges ;\n-   CVE-2012-0021 : \u003cspan class=\"textit\"\u003emod_log_config\u003c/span\u003e ne g\u00e8re\n    pas correctement certains cookies, ce qui peut conduire \u00e0 un arr\u00eat\n    inopin\u00e9 du service Apache ;\n-   CVE-2012-0031 : un probl\u00e8me dans la gestion des segments de m\u00e9moire\n    partag\u00e9e peut conduire \u00e0 un d\u00e9ni de service local ;\n-   CVE-2012-0053 : lorsqu\u0027aucune page personnalis\u00e9e n\u0027est d\u00e9finie pour\n    le code d\u0027erreur 400, il est possible d\u0027obtenir les cookies\n    httpOnly.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans HP-UX",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 HP-UX c03278391 du 18 avril 2012",
      "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.