CERTA-2011-AVI-363

Vulnerability from certfr_avis - Published: - Updated:

Une vulnérabilité découverte dans les produits Avaya permet, sous certaines conditions, un accés illégitime aux données présentes sur le serveur hébergeant cette solution.

Description

Un serveur TFTP vulnérable est présent dans les solutions Avaya B5800 Branch Gateway 6.X et Avaya IP Office. Un utilisateur malveillant sur le réseau local peut, sous certaines conditions, accéder de façon illégitime aux données présentes sur le serveur sur lequel cette solution est installée.

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
AVAYA N/A Avaya B5800 Branch Gateway 6.x ;
AVAYA N/A Avaya IP Office toutes versions.
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Avaya B5800 Branch Gateway 6.x ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "AVAYA",
          "scada": false
        }
      }
    },
    {
      "description": "Avaya IP Office toutes versions.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "AVAYA",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nUn serveur TFTP vuln\u00e9rable est pr\u00e9sent dans les solutions Avaya B5800\nBranch Gateway 6.X et Avaya IP Office. Un utilisateur malveillant sur le\nr\u00e9seau local peut, sous certaines conditions, acc\u00e9der de fa\u00e7on\nill\u00e9gitime aux donn\u00e9es pr\u00e9sentes sur le serveur sur lequel cette\nsolution est install\u00e9e.\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": [],
  "links": [],
  "reference": "CERTA-2011-AVI-363",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-06-17T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Contournement de la politique de s\u00e9curit\u00e9"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 d\u00e9couverte dans les produits Avaya permet, sous\ncertaines conditions, un acc\u00e9s ill\u00e9gitime aux donn\u00e9es pr\u00e9sentes sur le\nserveur h\u00e9bergeant cette solution.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans Avaya IP Office Manager",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Avaya ASA-2011-156 du 15 juin 2011",
      "url": "https://support.avaya.com/css/P8/documents/100141179"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…