njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://cwe.mitre.org/data/definitions/416.html | third party advisory |
https://github.com/nginx/njs/issues/324 | issue tracking patch exploit third party advisory |
https://security.netapp.com/advisory/ntap-20200918-0001/ | third party advisory |