Searched refs:get_ext (Results 1 – 2 of 2) sorted by relevance
/trusted-firmware-a-latest/docs/security_advisories/ |
D | security-advisory-tfv-10.rst | 16 | Affected | downstream usages of ``get_ext()`` and/or ``auth_nvctr()`` | 63 ``drivers/auth/mbedtls/mbedtls_x509_parser.c``. By design, ``get_ext()`` does 73 undefined on failure. In practice, this results in ``get_ext()`` continuing to 76 holds. The result is that it is possible for ``get_ext()`` to read memory past 94 ``get_ext()``, which means that the second bug is exploitable, so is the first. 99 validated prior to calling ``get_ext()``, or any function that calls ``get_ext()``. 102 always be done prior to any calls to ``get_ext()`` or ``auth_nvctr()`` in this 106 Furthermore, the data read through ``get_ext()`` only 109 impact this has. Specifically, the authentication framework uses ``get_ext()`` 124 In summary, there are 2 separate issues - one in ``get_ext()`` and another one [all …]
|
/trusted-firmware-a-latest/drivers/auth/mbedtls/ |
D | mbedtls_x509_parser.c | 72 static int get_ext(const char *oid, void **ext, unsigned int *ext_len) in get_ext() function 390 ret = get_ext(NULL, NULL, NULL); in cert_parse() 477 rc = get_ext(type_desc->cookie, param, param_len); in get_auth_param() 482 rc = get_ext(type_desc->cookie, param, param_len); in get_auth_param()
|