CERTA-2008-AVI-439

Vulnerability from certfr_avis - Published: 2008-09-04 - Updated: 2008-09-04

Une vulnérablité présente dans le noyau de FreeBSD permet à un utilisateur local d'exécuter du code arbitraire et d'élever ses privilèges.

Description

Une vulnérabilité est présente dans la gestion du changement de contexte entre espace utilisateur et espace noyau sur les systèmes FreeBSD pour architecture amd64. Cette faille permet à un utilisateur local d'exécuter du code arbitraire dans le contexte du noyau en provoquant volontairement un certain type d'erreur système de façon particulière.

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
FreeBSD N/A FreeBSD 6.3 ;
FreeBSD N/A FreeBSD 7.0.

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "FreeBSD 6.3 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "FreeBSD",
          "scada": false
        }
      }
    },
    {
      "description": "FreeBSD 7.0.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "FreeBSD",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 est pr\u00e9sente dans la gestion du changement de contexte\nentre espace utilisateur et espace noyau sur les syst\u00e8mes FreeBSD pour\narchitecture amd64. Cette faille permet \u00e0 un utilisateur local\nd\u0027ex\u00e9cuter du code arbitraire dans le contexte du noyau en provoquant\nvolontairement un certain type d\u0027erreur syst\u00e8me de fa\u00e7on particuli\u00e8re.\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-2008-3890",
      "url": "https://www.cve.org/CVERecord?id=CVE-2008-3890"
    }
  ],
  "initial_release_date": "2008-09-04T00:00:00",
  "last_revision_date": "2008-09-04T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 FreeBSD SA-08:07.amd64 du 03 septembre    2008 :",
      "url": "ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-08:07.amd64.asc"
    }
  ],
  "reference": "CERTA-2008-AVI-439",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2008-09-04T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire"
    },
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": "Une vuln\u00e9rablit\u00e9 pr\u00e9sente dans le noyau de FreeBSD permet \u00e0 un\nutilisateur local d\u0027ex\u00e9cuter du code arbitraire et d\u0027\u00e9lever ses\nprivil\u00e8ges.\n",
  "title": "Vuln\u00e9rabilit\u00e9 du noyau FreeBSD pour plateforme amd64",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 FreeBSD FreeBSD-SA-08:07.amd64",
      "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.