CERTA-2012-AVI-199
Vulnerability from certfr_avis - Published: 2012-04-10 - Updated: 2012-04-10
De multiples vulnérabilités ont été corrigées dans RealNetworks Helix server. Une concerne le stockage en clair des mots de passe sur disque. Deux autres permettent de provoquer un déni de service sur le service SNMP Manager Agent. Une vulnérabilité de type « débordement de tampon » affecte le traitement des identifiants et peut conduire à une exécution de code arbitraire à distance. La version 14.2.0.212 est affectée par une injection de code indirecte à distance (XSS). Enfin, le traitement d'URL spécialement formatées peut mener à un déni de service à distance.
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": "Helix Mobile Server version 14.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "Helix Server version 14.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## 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-2012-1923",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-1923"
},
{
"name": "CVE-2012-1985",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-1985"
},
{
"name": "CVE-2012-1984",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-1984"
},
{
"name": "CVE-2012-0942",
"url": "https://www.cve.org/CVERecord?id=CVE-2012-0942"
}
],
"initial_release_date": "2012-04-10T00:00:00",
"last_revision_date": "2012-04-10T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 RealNetworks Helix 04022012 du 02 avril 2012 :",
"url": "http://helixproducts.real.com/docs/security/SecurityUpdate04022012HS.pdf"
}
],
"reference": "CERTA-2012-AVI-199",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2012-04-10T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Injection de code indirecte \u00e0 distance"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans \u003cspan\nclass=\"textit\"\u003eRealNetworks Helix server\u003c/span\u003e. Une concerne le\nstockage en clair des mots de passe sur disque. Deux autres permettent\nde provoquer un d\u00e9ni de service sur le service \u003cspan class=\"textit\"\u003eSNMP\nManager Agent\u003c/span\u003e. Une vuln\u00e9rabilit\u00e9 de type \u00ab d\u00e9bordement de tampon\n\u00bb affecte le traitement des identifiants et peut conduire \u00e0 une\nex\u00e9cution de code arbitraire \u00e0 distance. La version 14.2.0.212 est\naffect\u00e9e par une injection de code indirecte \u00e0 distance (\u003cspan\nclass=\"textit\"\u003eXSS\u003c/span\u003e). Enfin, le traitement d\u0027URL sp\u00e9cialement\nformat\u00e9es peut mener \u00e0 un d\u00e9ni de service \u00e0 distance.\n",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans RealNetworks Helix",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 RealNetworks Helix 04022012 du 02 avril 2012",
"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.