CERTA-2011-AVI-724
Vulnerability from certfr_avis - Published: 2011-12-26 - Updated: 2011-12-26
Une vulnérabilité permettant à un utilisateur malintentionné distant de causer un déni de service est présente dans IBM Lotus Domino Server.
Description
Une vulnérabilité est présente dans IBM Lotus Domino Server. Elle permet à une personne malintentionnée de causer un déni de service grâce à l'envoi d'un paquet spécialement conçu via Notes RPC.
L'attaquant doit disposer de capacités de surveillance du traffic réseau entre le client Notes et le serveur Domino afin de mener son attaque à bien.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "IBM Lotus Domino Server 8.5 ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "IBM Lotus Domino Server 8.5.1 ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "IBM Lotus Domino Server version 8.5.2 FP3 et ant\u00e9rieures ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "IBM Lotus Domino Server 8.0.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 est pr\u00e9sente dans IBM Lotus Domino Server. Elle permet\n\u00e0 une personne malintentionn\u00e9e de causer un d\u00e9ni de service gr\u00e2ce \u00e0\nl\u0027envoi d\u0027un paquet sp\u00e9cialement con\u00e7u via Notes RPC.\n\nL\u0027attaquant doit disposer de capacit\u00e9s de surveillance du traffic r\u00e9seau\nentre le client Notes et le serveur Domino afin de mener son attaque \u00e0\nbien.\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-1393",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-1393"
}
],
"initial_release_date": "2011-12-26T00:00:00",
"last_revision_date": "2011-12-26T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 IBM ISS X-Force xfdb/71805 du 14 d\u00e9cembre 2011 :",
"url": "http://xforce.iss.net/xforce/xfdb/71805"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 IBM swg21575247 du 21 d\u00e9cembre 2011 :",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21575247"
}
],
"reference": "CERTA-2011-AVI-724",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-12-26T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 permettant \u00e0 un utilisateur malintentionn\u00e9 distant de\ncauser un d\u00e9ni de service est pr\u00e9sente dans \u003cspan class=\"textit\"\u003eIBM\nLotus Domino Server\u003c/span\u003e.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans IBM Lotus Domino",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 IBM 1575247 du 21 d\u00e9cembre 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.