CERTA-2006-AVI-108

Vulnerability from certfr_avis - Published: 2006-03-14 - Updated: 2006-03-14

None

Description

De multiples vulnérabilités existent dans la version actuelle de Mac 0S X v.10.4.5. Parmi les services impactés, nous notons :

  • Mail : Une personne malveillante peut envoyer un courriel particulier avec pièces jointes, afin d'inciter l'utilisateur à ouvrir celles-ci. Cette action peut entraîner un dépassement de tampon permettant l'exécution de code arbitraire sur le système. Le problème n'existe pas pour les versions Mac OS antérieures à 10.4.
  • Safari, LaunchServices : Safari ouvre automatiquement des fichiers courants, comme les images ou les vidéos. Une personne malveillante peut alors insérer sur son site un code ayant une telle apparence, afin d'exécuter un code arbitraire à distance. Le problème n'existe pas pour les versions de Mac OS antérieures à 10.4.
  • CoreTypes : Une page contenant un code JavaScript malveillant permet d'accéder et modifier des documents d'origine différente (voir la notion sous Mac OS de Same-Origin, une origine étant un triplet constitué par le protocole, le port et le serveur Internet).

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
Apple macOS Mac OS X version 10.4.5
Apple macOS Mac OS X Server version 10.4.5
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Mac OS X version 10.4.5",
      "product": {
        "name": "macOS",
        "vendor": {
          "name": "Apple",
          "scada": false
        }
      }
    },
    {
      "description": "Mac OS X Server version 10.4.5",
      "product": {
        "name": "macOS",
        "vendor": {
          "name": "Apple",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nDe multiples vuln\u00e9rabilit\u00e9s existent dans la version actuelle de Mac 0S\nX v.10.4.5. Parmi les services impact\u00e9s, nous notons :\n\n-   Mail : Une personne malveillante peut envoyer un courriel\n    particulier avec pi\u00e8ces jointes, afin d\u0027inciter l\u0027utilisateur \u00e0\n    ouvrir celles-ci. Cette action peut entra\u00eener un d\u00e9passement de\n    tampon permettant l\u0027ex\u00e9cution de code arbitraire sur le syst\u00e8me. Le\n    probl\u00e8me n\u0027existe pas pour les versions Mac OS ant\u00e9rieures \u00e0 10.4.\n-   Safari, LaunchServices : Safari ouvre automatiquement des fichiers\n    courants, comme les images ou les vid\u00e9os. Une personne malveillante\n    peut alors ins\u00e9rer sur son site un code ayant une telle apparence,\n    afin d\u0027ex\u00e9cuter un code arbitraire \u00e0 distance. Le probl\u00e8me n\u0027existe\n    pas pour les versions de Mac OS ant\u00e9rieures \u00e0 10.4.\n-   CoreTypes : Une page contenant un code JavaScript malveillant permet\n    d\u0027acc\u00e9der et modifier des documents d\u0027origine diff\u00e9rente (voir la\n    notion sous Mac OS de Same-Origin, une origine \u00e9tant un triplet\n    constitu\u00e9 par le protocole, le port et le serveur Internet).\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-2006-0397",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0397"
    },
    {
      "name": "CVE-2006-0398",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0398"
    },
    {
      "name": "CVE-2006-0399",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0399"
    },
    {
      "name": "CVE-2006-0396",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0396"
    },
    {
      "name": "CVE-2006-0400",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-0400"
    }
  ],
  "initial_release_date": "2006-03-14T00:00:00",
  "last_revision_date": "2006-03-14T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Apple du 13 mars 2006 :",
      "url": "http://docs.info.apple.com/article.html?artnum=303453"
    }
  ],
  "reference": "CERTA-2006-AVI-108",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-03-14T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    },
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": null,
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans MacOS",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Mise \u00e0 jour s\u00e9curit\u00e9 de l\u0027\u00e9diteur Apple",
      "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.