nvd-json-data-feeds/CVE-2021/CVE-2021-09xx/CVE-2021-0942.json

{
  "id": "CVE-2021-0942",
  "sourceIdentifier": "security@android.com",
  "published": "2022-09-13T20:15:08.983",
  "lastModified": "2024-11-21T05:43:17.090",
  "vulnStatus": "Modified",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The path in this case is a little bit convoluted. The end result is that via an ioctl an untrusted app can control the ui32PageIndex offset in the expression:sPA.uiAddr = page_to_phys(psOSPageArrayData->pagearray[ui32PageIndex]);With the current PoC this crashes as an OOB read. However, given that the OOB read value is ending up as the address field of a struct I think i seems plausible that this could lead to an OOB write if the attacker is able to cause the OOB read to pull an interesting kernel address. Regardless if this is a read or write, it is a High severity issue in the kernel.Product: AndroidVersions: Android SoCAndroid ID: A-238904312"
    },
    {
      "lang": "es",
      "value": "El camino en este caso es un poco enrevesado. El resultado final es que por medio de un ioctl una app no confiable puede controlar el offset ui32PageIndex en la expresi\u00f3n:sPA.uiAddr = page_to_phys(psOSPageArrayData->pagearray[ui32PageIndex]);Con el PoC actual esto falla como una lectura OOB. Sin embargo, dado que el valor de la lectura OOB est\u00e1 terminando como el campo de direcci\u00f3n de una estructura, creo que parece plausible que esto podr\u00eda conllevar a una escritura OOB si el atacante es capaz de causar la lectura OOB para obtener una direcci\u00f3n interesante del kernel. Independientemente de si es tratado de una lectura o escritura, es un problema de Alta gravedad en el kernel.Product: Android, Versiones: Android SoC, ID de Android: A-238904312"
    }
  ],
  "metrics": {
    "cvssMetricV31": [
      {
        "source": "nvd@nist.gov",
        "type": "Primary",
        "cvssData": {
          "version": "3.1",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "baseScore": 9.8,
          "baseSeverity": "CRITICAL",
          "attackVector": "NETWORK",
          "attackComplexity": "LOW",
          "privilegesRequired": "NONE",
          "userInteraction": "NONE",
          "scope": "UNCHANGED",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "availabilityImpact": "HIGH"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.9
      }
    ]
  },
  "weaknesses": [
    {
      "source": "nvd@nist.gov",
      "type": "Primary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-125"
        }
      ]
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "operator": "OR",
          "negate": false,
          "cpeMatch": [
            {
              "vulnerable": true,
              "criteria": "cpe:2.3:o:google:android:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "F8B9FEC8-73B6-43B8-B24E-1F7C20D91D26"
            }
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "url": "https://source.android.com/security/bulletin/2022-09-01",
      "source": "security@android.com",
      "tags": [
        "Vendor Advisory"
      ]
    },
    {
      "url": "https://source.android.com/security/bulletin/2022-09-01",
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Vendor Advisory"
      ]
    }
  ]
}