CVE-2020-10255 (GCVE-0-2020-10255)

Vulnerability from cvelistv5 – Published: 2020-03-10 15:59 – Updated: 2024-08-04 10:58
VLAI
Summary
Modern DRAM chips (DDR4 and LPDDR4 after 2015) are affected by a vulnerability in deployment of internal mitigations against RowHammer attacks known as Target Row Refresh (TRR), aka the TRRespass issue. To exploit this vulnerability, the attacker needs to create certain access patterns to trigger bit flips on affected memory modules, aka a Many-sided RowHammer attack. This means that, even when chips advertised as RowHammer-free are used, attackers may still be able to conduct privilege-escalation attacks against the kernel, conduct privilege-escalation attacks against the Sudo binary, and achieve cross-tenant virtual-machine access by corrupting RSA keys. The issue affects chips produced by SK Hynix, Micron, and Samsung. NOTE: tracking DRAM supply-chain issues is not straightforward because a single product model from a single vendor may use DRAM chips from different manufacturers.
CWE
  • n/a
Assigner
mitre CNA under the mitre root
CNA scorecard E 29/100 over 2126 records in the last 180 days details
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T10:58:40.157Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://download.vusec.net/papers/trrespass_sp20.pdf"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://www.vusec.net/projects/trrespass/"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/vusec/trrespass"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://twitter.com/vu5ec/status/1237399112590467072"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://twitter.com/antumbral/status/1237425959407513600"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://thehackernews.com/2020/03/rowhammer-vulnerability-ddr4-dram.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Modern DRAM chips (DDR4 and LPDDR4 after 2015) are affected by a vulnerability in deployment of internal mitigations against RowHammer attacks known as Target Row Refresh (TRR), aka the TRRespass issue. To exploit this vulnerability, the attacker needs to create certain access patterns to trigger bit flips on affected memory modules, aka a Many-sided RowHammer attack. This means that, even when chips advertised as RowHammer-free are used, attackers may still be able to conduct privilege-escalation attacks against the kernel, conduct privilege-escalation attacks against the Sudo binary, and achieve cross-tenant virtual-machine access by corrupting RSA keys. The issue affects chips produced by SK Hynix, Micron, and Samsung. NOTE: tracking DRAM supply-chain issues is not straightforward because a single product model from a single vendor may use DRAM chips from different manufacturers."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2020-03-11T13:43:50.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://download.vusec.net/papers/trrespass_sp20.pdf"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://www.vusec.net/projects/trrespass/"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/vusec/trrespass"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://twitter.com/vu5ec/status/1237399112590467072"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://twitter.com/antumbral/status/1237425959407513600"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://thehackernews.com/2020/03/rowhammer-vulnerability-ddr4-dram.html"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2020-10255",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "Modern DRAM chips (DDR4 and LPDDR4 after 2015) are affected by a vulnerability in deployment of internal mitigations against RowHammer attacks known as Target Row Refresh (TRR), aka the TRRespass issue. To exploit this vulnerability, the attacker needs to create certain access patterns to trigger bit flips on affected memory modules, aka a Many-sided RowHammer attack. This means that, even when chips advertised as RowHammer-free are used, attackers may still be able to conduct privilege-escalation attacks against the kernel, conduct privilege-escalation attacks against the Sudo binary, and achieve cross-tenant virtual-machine access by corrupting RSA keys. The issue affects chips produced by SK Hynix, Micron, and Samsung. NOTE: tracking DRAM supply-chain issues is not straightforward because a single product model from a single vendor may use DRAM chips from different manufacturers."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://download.vusec.net/papers/trrespass_sp20.pdf",
              "refsource": "MISC",
              "url": "https://download.vusec.net/papers/trrespass_sp20.pdf"
            },
            {
              "name": "https://www.vusec.net/projects/trrespass/",
              "refsource": "MISC",
              "url": "https://www.vusec.net/projects/trrespass/"
            },
            {
              "name": "https://github.com/vusec/trrespass",
              "refsource": "MISC",
              "url": "https://github.com/vusec/trrespass"
            },
            {
              "name": "https://twitter.com/vu5ec/status/1237399112590467072",
              "refsource": "MISC",
              "url": "https://twitter.com/vu5ec/status/1237399112590467072"
            },
            {
              "name": "https://twitter.com/antumbral/status/1237425959407513600",
              "refsource": "MISC",
              "url": "https://twitter.com/antumbral/status/1237425959407513600"
            },
            {
              "name": "https://thehackernews.com/2020/03/rowhammer-vulnerability-ddr4-dram.html",
              "refsource": "MISC",
              "url": "https://thehackernews.com/2020/03/rowhammer-vulnerability-ddr4-dram.html"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2020-10255",
    "datePublished": "2020-03-10T15:59:59.000Z",
    "dateReserved": "2020-03-09T00:00:00.000Z",
    "dateUpdated": "2024-08-04T10:58:40.157Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2020-10255",
      "date": "2026-11-16",
      "epss": "0.02427",
      "percentile": "0.84492"
    },
    "nvd": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:h:micron:ddr4_sdram:-:*:*:*:*:*:*:*",
                    "matchCriteriaId": "C61E4ABB-8D8E-4EF0-9FCC-864DCA8862BA",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:h:micron:lpddr4:-:*:*:*:*:*:*:*",
                    "matchCriteriaId": "4024237B-254C-4A65-8263-12FED692D155",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:h:samsung:ddr4:-:*:*:*:*:*:*:*",
                    "matchCriteriaId": "D9704C77-A81A-4C71-9CD5-43D2C90EF574",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:h:samsung:lpddr4:-:*:*:*:*:*:*:*",
                    "matchCriteriaId": "51C71653-2974-4151-98A9-831E5C08C5D4",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:h:skhynix:ddr4_sdram:-:*:*:*:*:*:*:*",
                    "matchCriteriaId": "582FC9BC-EC95-4002-944C-4453879108F8",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:h:skhynix:lpddr4:-:*:*:*:*:*:*:*",
                    "matchCriteriaId": "429192DE-1D08-488F-93A6-3F5F467FC210",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Modern DRAM chips (DDR4 and LPDDR4 after 2015) are affected by a vulnerability in deployment of internal mitigations against RowHammer attacks known as Target Row Refresh (TRR), aka the TRRespass issue. To exploit this vulnerability, the attacker needs to create certain access patterns to trigger bit flips on affected memory modules, aka a Many-sided RowHammer attack. This means that, even when chips advertised as RowHammer-free are used, attackers may still be able to conduct privilege-escalation attacks against the kernel, conduct privilege-escalation attacks against the Sudo binary, and achieve cross-tenant virtual-machine access by corrupting RSA keys. The issue affects chips produced by SK Hynix, Micron, and Samsung. NOTE: tracking DRAM supply-chain issues is not straightforward because a single product model from a single vendor may use DRAM chips from different manufacturers."
          },
          {
            "lang": "es",
            "value": "Los chips DRAM modernos (DDR4 y LPDDR4 despu\u00e9s de 2015) est\u00e1n afectados por una vulnerabilidad en la implementaci\u00f3n de mitigaciones internas contra los ataques de tipo RowHammer conocido como Target Row Refresh (TRR), tambi\u00e9n se conoce como el problema TRRespass. Para explotar esta vulnerabilidad, el atacante requiere crear determinados patrones de acceso para activar cambios de bits sobre los m\u00f3dulos de memoria afectados, tambi\u00e9n se conoce como un ataque de tipo RowHammer de Muchos Flancos. Esto significa que, incluso cuando son usados chips anunciados como RowHammer-free, los atacantes a\u00fan pueden ser capaces de dirigir ataques de escalada de privilegios contra el kernel, conducir ataques de escalada de privilegios contra el binario Sudo y lograr el acceso a m\u00e1quinas virtuales entre inquilinos al corromper claves RSA. El problema afecta a los chips producidos por SK Hynix, Micron y Samsung. NOTA: el seguimiento de los problemas de la cadena de suministro de DRAM no es sencillo porque un solo modelo de producto de un \u00fanico proveedor puede usar chips DRAM de diferentes fabricantes."
          }
        ],
        "id": "CVE-2020-10255",
        "lastModified": "2024-11-21T04:55:04.710",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": false,
              "baseSeverity": "HIGH",
              "cvssData": {
                "accessComplexity": "MEDIUM",
                "accessVector": "NETWORK",
                "authentication": "NONE",
                "availabilityImpact": "COMPLETE",
                "baseScore": 9.3,
                "confidentialityImpact": "COMPLETE",
                "integrityImpact": "COMPLETE",
                "vectorString": "AV:N/AC:M/Au:N/C:C/I:C/A:C",
                "version": "2.0"
              },
              "exploitabilityScore": 8.6,
              "impactScore": 10.0,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": false
            }
          ],
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 9.0,
                "baseSeverity": "CRITICAL",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "privilegesRequired": "NONE",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 2.2,
              "impactScore": 6.0,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2020-03-10T16:15:15.990",
        "references": [
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://download.vusec.net/papers/trrespass_sp20.pdf"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Product"
            ],
            "url": "https://github.com/vusec/trrespass"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://thehackernews.com/2020/03/rowhammer-vulnerability-ddr4-dram.html"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://twitter.com/antumbral/status/1237425959407513600"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://twitter.com/vu5ec/status/1237399112590467072"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://www.vusec.net/projects/trrespass/"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://download.vusec.net/papers/trrespass_sp20.pdf"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Product"
            ],
            "url": "https://github.com/vusec/trrespass"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://thehackernews.com/2020/03/rowhammer-vulnerability-ddr4-dram.html"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://twitter.com/antumbral/status/1237425959407513600"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://twitter.com/vu5ec/status/1237399112590467072"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Third Party Advisory"
            ],
            "url": "https://www.vusec.net/projects/trrespass/"
          }
        ],
        "sourceIdentifier": "cve@mitre.org",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-20"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Important",
      "current_release_date": "2026-11-04T20:48:58+00:00",
      "cve": "CVE-2020-10255",
      "id": "CVE-2020-10255",
      "initial_release_date": "2020-03-10T15:00:00+00:00",
      "product_status:known_not_affected": "63",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "hw: dram: circumvent TRR to induce bit flips via Rowhammer",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-10255.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.