CERTA-2011-AVI-102
Vulnerability from certfr_avis - Published: 2011-02-23 - Updated: 2011-02-23
Plusieurs vulnérabilités dans l'annuaire RedHat Directory Server permettent à un utilisateur malveillant de provoquer un déni de service à distance ou d'élever ses privilèges.
Description
Trois vulnérabilités de RedHat Directory Server viennent d'être corrigées :
- le lancement simultané de recherches d'un certain type par un utilisateur distant non authentifié permet de provoquer un arrêt inopiné du serveur ;
- un défaut de positionnement des droits existe quand plusieurs serveurs annuaire s'exécutent sur la même machine, avec des comptes système non privilégiés. Ce défaut est exploitable par un utilisateur malveillant local pour provoquer un déni de service ;
- plusieurs scripts accompagnant le paquet RedHat Directory Server donnent à une variable d'environnement une valeur vide. Ceci peut être mis à profit par un utilisateur local pour élever ses privilèges.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
RedHat Directory Server v8 EL4 et EL5.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cp\u003eRedHat Directory Server v8 EL4 et EL5.\u003c/p\u003e",
"content": "## Description\n\nTrois vuln\u00e9rabilit\u00e9s de RedHat Directory Server viennent d\u0027\u00eatre\ncorrig\u00e9es\u00a0:\n\n- le lancement simultan\u00e9 de recherches d\u0027un certain type par un\n utilisateur distant non authentifi\u00e9 permet de provoquer un arr\u00eat\n inopin\u00e9 du serveur\u00a0;\n- un d\u00e9faut de positionnement des droits existe quand plusieurs\n serveurs annuaire s\u0027ex\u00e9cutent sur la m\u00eame machine, avec des comptes\n syst\u00e8me non privil\u00e9gi\u00e9s. Ce d\u00e9faut est exploitable par un\n utilisateur malveillant local pour provoquer un d\u00e9ni de service\u00a0;\n- plusieurs scripts accompagnant le paquet RedHat Directory Server\n donnent \u00e0 une variable d\u0027environnement une valeur vide. Ceci peut\n \u00eatre mis \u00e0 profit par un utilisateur local pour \u00e9lever ses\n privil\u00e8ges.\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-2011-0019",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-0019"
},
{
"name": "CVE-2011-0532",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-0532"
},
{
"name": "CVE-2011-0022",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-0022"
}
],
"initial_release_date": "2011-02-23T00:00:00",
"last_revision_date": "2011-02-23T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 RedHat RHSA-2011:0293 du 22 f\u00e9vrier 2011 :",
"url": "http://rhn.redhat.com/errata/RHSA-2011-0293.html"
}
],
"reference": "CERTA-2011-AVI-102",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-02-23T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s dans l\u0027annuaire RedHat Directory Server\npermettent \u00e0 un utilisateur malveillant de provoquer un d\u00e9ni de service\n\u00e0 distance ou d\u0027\u00e9lever ses privil\u00e8ges.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans RedHat Directory Server",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 RedHat RHSA-2011:0293 du 22 f\u00e9vrier 2011",
"url": null
}
]
}
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.
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
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.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.