CERTA-2011-AVI-587
Vulnerability from certfr_avis - Published: 2011-10-21 - Updated: 2011-10-21
Deux vulnérabilités dans Splunk permettent de réaliser un déni de service et d'injecter du code indirectement à distance.
Description
Deux vulnérabilités ont été découvertes dans le composant Splunk Web de Splunk. La première permet d'injecter du code indirectement, en incitant un utilisateur à suivre un lien spécifiquement constitué. La seconde permet d'épuiser les ressources du système.
Solution
Se référer aux bulletins de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Splunk versions 4.0 à 4.2.3 (incluses).
Impacted products
| Vendor | Product | Description |
|---|
References
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cP\u003e\u003cSPAN class=\"textit\"\u003eSplunk\u003c/SPAN\u003e versions 4.0 \u00e0 4.2.3 (incluses).\u003c/P\u003e",
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans le composant Splunk Web de\nSplunk. La premi\u00e8re permet d\u0027injecter du code indirectement, en incitant\nun utilisateur \u00e0 suivre un lien sp\u00e9cifiquement constitu\u00e9. La seconde\npermet d\u0027\u00e9puiser les ressources du syst\u00e8me.\n\n## Solution\n\nSe r\u00e9f\u00e9rer aux bulletins de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [],
"initial_release_date": "2011-10-21T00:00:00",
"last_revision_date": "2011-10-21T00:00:00",
"links": [
{
"title": "Bulletins de s\u00e9curit\u00e9 Splunk SPL-42471 et SPL-42474 du 19 octobre 2011 :",
"url": "http://www.splunk.com/view/SP-CAAAGGH"
}
],
"reference": "CERTA-2011-AVI-587",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-10-21T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Injection de code indirecte \u00e0 distance"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s dans \u003cspan class=\"textit\"\u003eSplunk\u003c/span\u003e permettent\nde r\u00e9aliser un d\u00e9ni de service et d\u0027injecter du code indirectement \u00e0\ndistance.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans Splunk",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 Splunk SPL-42471 et SPL-42474 du 19 octobre 2011",
"url": null
}
]
}
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…
Loading…