CERTA-2010-AVI-418

Vulnerability from certfr_avis - Published: 2010-09-06 - Updated: 2010-10-06

MantisBT présente deux vulnérabilités de type injection de code indirecte (XSS).

Description

MantisBT est un outil de gestion des erreurs de programme (bug tracker).

Deux vulnérabilités de type XSS l'affectent :

  • le rendu des pièces jointes intégrées permet l'injection de code HTML ou de scripts ;
  • la fonction project_id_filter_target permet de réaliser de l'injection de code indirecte quand le filtrage avancé des vues est utilisé.

Solution

La version MantisBT 1.2.2 remédie à ces vulnérabilités.

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

MantisBT, versions antérieures à la version 1.2.2.

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\u003eMantisBT, versions ant\u00e9rieures \u00e0 la  version 1.2.2.\u003c/p\u003e",
  "content": "## Description\n\nMantisBT est un outil de gestion des erreurs de programme (bug tracker).\n\nDeux vuln\u00e9rabilit\u00e9s de type XSS l\u0027affectent\u00a0:\n\n-   le rendu des pi\u00e8ces jointes int\u00e9gr\u00e9es permet l\u0027injection de code\n    HTML ou de scripts\u00a0;\n-   la fonction project_id_filter_target permet de r\u00e9aliser de\n    l\u0027injection de code indirecte quand le filtrage avanc\u00e9 des vues est\n    utilis\u00e9.\n\n## Solution\n\nLa version MantisBT 1.2.2 rem\u00e9die \u00e0 ces vuln\u00e9rabilit\u00e9s.\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-2010-2802",
      "url": "https://www.cve.org/CVERecord?id=CVE-2010-2802"
    },
    {
      "name": "CVE-2010-2574",
      "url": "https://www.cve.org/CVERecord?id=CVE-2010-2574"
    }
  ],
  "initial_release_date": "2010-09-06T00:00:00",
  "last_revision_date": "2010-10-06T00:00:00",
  "links": [
    {
      "title": "Site de t\u00e9l\u00e9chargement du projet MantisBT :",
      "url": "http://www.mantisbt.org/download.php"
    }
  ],
  "reference": "CERTA-2010-AVI-418",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2010-09-06T00:00:00.000000"
    },
    {
      "description": "ajout des r\u00e9f\u00e9rences CVE.",
      "revision_date": "2010-10-06T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Injection de code indirecte \u00e0 distance"
    }
  ],
  "summary": "MantisBT pr\u00e9sente deux vuln\u00e9rabilit\u00e9s de type injection de code\nindirecte (XSS).\n",
  "title": "Vuln\u00e9rabilit\u00e9s dans MantisBT",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de version de MantisBT du 29 juillet 2010",
      "url": "http://www.mantisbt.org/bugs/changelog_page.php?version_id=110"
    }
  ]
}



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

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.