CERTA-2006-AVI-216
Vulnerability from certfr_avis - Published: 2006-05-24 - Updated: 2006-08-21
Deux vulnérabilités ont été identifiées dans PostgreSQL. Elles peuvent être utilisées par une personne malveillante pour injecter des requêtes SQL, afin d'accéder ou modifier les données inclues dans la base, et ainsi contourner la politique de sécurité.
Description
PostgreSQL est un système de gestion de bases de données (DBMS). Deux vulnérabilités ont été identifiées dans certaines versions du serveur. Il ne contrôle pas correctement certains caractères d'échappement, tels que le guillemet '. Un utilisateur malveillant peut profiter de ce problème pour injecter, soit directement, soit par le biais d'une application tierce, des requêtes SQL arbitraires. La politique de sécurité est alors contournée.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| PostgreSQL | PostgreSQL | La version PostgreSQL 7.3.14 et les versions 7.3.x antérieures ; | ||
| PostgreSQL | PostgreSQL | la version PostgreSQL 7.4.12 et les versions 7.4.x antérieures ; | ||
| PostgreSQL | PostgreSQL | la version PostgreSQL 8.1.3 et les versions 8.1.x antérieures. | ||
| PostgreSQL | PostgreSQL | la version PostgreSQL 8.0.7 et les versions 8.0.x antérieures ; |
| Title | Publication Time | Tags | |
|---|---|---|---|
|
|
|||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "La version PostgreSQL 7.3.14 et les versions 7.3.x ant\u00e9rieures ;",
"product": {
"name": "PostgreSQL",
"vendor": {
"name": "PostgreSQL",
"scada": false
}
}
},
{
"description": "la version PostgreSQL 7.4.12 et les versions 7.4.x ant\u00e9rieures ;",
"product": {
"name": "PostgreSQL",
"vendor": {
"name": "PostgreSQL",
"scada": false
}
}
},
{
"description": "la version PostgreSQL 8.1.3 et les versions 8.1.x ant\u00e9rieures.",
"product": {
"name": "PostgreSQL",
"vendor": {
"name": "PostgreSQL",
"scada": false
}
}
},
{
"description": "la version PostgreSQL 8.0.7 et les versions 8.0.x ant\u00e9rieures ;",
"product": {
"name": "PostgreSQL",
"vendor": {
"name": "PostgreSQL",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nPostgreSQL est un syst\u00e8me de gestion de bases de donn\u00e9es (DBMS). Deux\nvuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans certaines versions du serveur.\nIl ne contr\u00f4le pas correctement certains caract\u00e8res d\u0027\u00e9chappement, tels\nque le guillemet \u0027. Un utilisateur malveillant peut profiter de ce\nprobl\u00e8me pour injecter, soit directement, soit par le biais d\u0027une\napplication tierce, des requ\u00eates SQL arbitraires. La politique de\ns\u00e9curit\u00e9 est alors contourn\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": [
{
"name": "CVE-2006-2314",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-2314"
},
{
"name": "CVE-2006-2313",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-2313"
}
],
"initial_release_date": "2006-05-24T00:00:00",
"last_revision_date": "2006-08-21T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Mandriva MDKSA-2006:098 du 07 juin 2006 :",
"url": "http://www.mandriva.com/security/advisories?name=MDKSA-2006:098"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 PostgreSQL du 22 mai 2006 :",
"url": "http://www.postgresql.org/docs/techdocs.50"
},
{
"title": "Page de mise \u00e0 jour PostgreSQL :",
"url": "http://www.postgresql.org/download"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Debian DSA-1087 du 03 juin 2006 :",
"url": "http://www.debian.org/security/2006/dsa-1087"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 FreeBSD :",
"url": "http://www.vuxml.org/freebsd/pkg-ja-postgresql.html"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 RedHat du 26 mai 2006 :",
"url": "http://rhn.redhat.com/errata/RHSA-2006-0526.html"
}
],
"reference": "CERTA-2006-AVI-216",
"revisions": [
{
"description": "version initiale ;",
"revision_date": "2006-05-24T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 RedHat.",
"revision_date": "2006-05-26T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 Debian.",
"revision_date": "2006-06-06T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 Mandriva.",
"revision_date": "2006-06-08T00:00:00.000000"
},
{
"description": "ajout de la r\u00e9f\u00e9rence au bulletin de s\u00e9curit\u00e9 FreeBSD.",
"revision_date": "2006-08-21T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans PostgreSQL. Elles peuvent\n\u00eatre utilis\u00e9es par une personne malveillante pour injecter des requ\u00eates\nSQL, afin d\u0027acc\u00e9der ou modifier les donn\u00e9es inclues dans la base, et\nainsi contourner la politique de s\u00e9curit\u00e9.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans PostgreSQL",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 postgreSQL du 22 mai 2006",
"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.