CERTA-2008-AVI-252

Vulnerability from certfr_avis - Published: - Updated:

Plusieurs vulnérabilités présentes dans le noyau Linux permettent à un utilisateur distant de provoquer un déni de service ou à un utilisateur local de contourner la politique de sécurité du système.

Description

Plusieurs vulnérabilités sont présentes dans le noyau Linux :

  • la première est relative à l'appel système sys_utimensat(). Elle permet à un utilisateur local de modifier les dates d'accès ou de modifications d'un fichier arbitraire sans tenir compte des droits d'accès normaux ;
  • la deuxième concerne le pilote mettant en œuvre l'encapsulation IPv6 dans IPv4 et permet à un utilisateur distant de provoquer une consommation excessive de la mémoire via un paquet particulier ;
  • la dernière concerne la fonction mmap() sur architecture de type SPARC. Cette vulnérabilité permet à un utilisateur local de provoquer un déni de service du système vulnérable.

Solution

La version 2.6.25.3 du noyau Linux corrige le problème :

http://www.kernel.org

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

Les noyaux Linux versions 2.6.25.2 et antérieures.

Impacted products
Vendor Product Description
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cp\u003eLes noyaux Linux versions 2.6.25.2 et  ant\u00e9rieures.\u003c/p\u003e",
  "content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s sont pr\u00e9sentes dans le noyau Linux :\n\n-   la premi\u00e8re est relative \u00e0 l\u0027appel syst\u00e8me sys_utimensat(). Elle\n    permet \u00e0 un utilisateur local de modifier les dates d\u0027acc\u00e8s ou de\n    modifications d\u0027un fichier arbitraire sans tenir compte des droits\n    d\u0027acc\u00e8s normaux ;\n-   la deuxi\u00e8me concerne le pilote mettant en \u0153uvre l\u0027encapsulation IPv6\n    dans IPv4 et permet \u00e0 un utilisateur distant de provoquer une\n    consommation excessive de la m\u00e9moire via un paquet particulier ;\n-   la derni\u00e8re concerne la fonction mmap() sur architecture de type\n    SPARC. Cette vuln\u00e9rabilit\u00e9 permet \u00e0 un utilisateur local de\n    provoquer un d\u00e9ni de service du syst\u00e8me vuln\u00e9rable.\n\n## Solution\n\nLa version 2.6.25.3 du noyau Linux corrige le probl\u00e8me :\n\n    http://www.kernel.org\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 des \u00e9diteurs de distributions pour\nl\u0027obtention de correctifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2008-2148",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-2148"
    },
    {
      "name": "CVE-2008-2137",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-2137"
    },
    {
      "name": "CVE-2008-2136",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-2136"
    }
  ],
  "links": [
    {
      "title": "Liste des changements apport\u00e9s dans la version 2.6.25.3 du    noyau Linux :",
      "url": "http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.25.3"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 OpenSUSE SUSE-SA:2008:030 du 20 juin    2008 :",
      "url": "http://lists.opensuse.org/opensuse-security-announce/2008-06/msg00006.html"
    }
  ],
  "reference": "CERTA-2008-AVI-252",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2008-05-19T00:00:00.000000"
    },
    {
      "description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 OpenSUSE.",
      "revision_date": "2008-06-25T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s pr\u00e9sentes dans le noyau Linux permettent \u00e0 un\nutilisateur distant de provoquer un d\u00e9ni de service ou \u00e0 un utilisateur\nlocal de contourner la politique de s\u00e9curit\u00e9 du syst\u00e8me.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s du noyau Linux",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Liste des changements apport\u00e9s dans la version 2.6.25.3 du noyau Linux",
      "url": null
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Loading timeline…




    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.