CERTA-2007-AVI-444

Vulnerability from certfr_avis - Published: 2007-10-18 - Updated: 2007-10-18

Une vulnérabilité a été identifiée dans le logiciel de manipulation d'images IrfanView. Elle permettrait à une personne malveillante d'exécuter, par le biais d'un fichier spécialement construit, du code arbitraire sur le système ayant une version vulnérable.

Description

Une vulnérabilité a été identifiée dans le logiciel de manipulation d'images IrfanView. Il ne manipulerait pas correctement des fichiers au format .PAL définissant des palettes de couleurs.

Cette vulnérabilité pourrait être exploitée par une personne malveillante avec un fichier .pal spécialement construit. Son importation dans une version d'IrfanView vulnérable permettrait alors l'exécution de code sur le système.

Solution

Se référer au bulletin de mise à jour pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
N/A N/A IrfanView version 4.00.
N/A N/A IrfanView version 3.99 ;

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "IrfanView version 4.00.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    },
    {
      "description": "IrfanView version 3.99 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "N/A",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans le logiciel de manipulation\nd\u0027images IrfanView. Il ne manipulerait pas correctement des fichiers au\nformat .PAL d\u00e9finissant des palettes de couleurs.\n\nCette vuln\u00e9rabilit\u00e9 pourrait \u00eatre exploit\u00e9e par une personne\nmalveillante avec un fichier .pal sp\u00e9cialement construit. Son\nimportation dans une version d\u0027IrfanView vuln\u00e9rable permettrait alors\nl\u0027ex\u00e9cution de code sur le syst\u00e8me.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de mise \u00e0 jour pour l\u0027obtention des correctifs\n(cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2007-4343",
      "url": "https://www.cve.org/CVERecord?id=CVE-2007-4343"
    }
  ],
  "initial_release_date": "2007-10-18T00:00:00",
  "last_revision_date": "2007-10-18T00:00:00",
  "links": [
    {
      "title": "Alerte de Secunia num\u00e9ro 2007-71 du 16 octobre 2007 :",
      "url": "http://secunia.com/secunia_research/2007-71/advisory/"
    },
    {
      "title": "Avis de changement de version 4.10 IrfanView du 15 octobre    2007 :",
      "url": "http://www.irfanview.com"
    }
  ],
  "reference": "CERTA-2007-AVI-444",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2007-10-18T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans le logiciel de manipulation\nd\u0027images IrfanView. Elle permettrait \u00e0 une personne malveillante\nd\u0027ex\u00e9cuter, par le biais d\u0027un fichier sp\u00e9cialement construit, du code\narbitraire sur le syst\u00e8me ayant une version vuln\u00e9rable.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans IrfanView",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Avis de changement de version 4.10 IrfanView du 15 octobre 2007",
      "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.