{"id":4639,"date":"2023-09-05T19:23:15","date_gmt":"2023-09-05T19:23:15","guid":{"rendered":"http:\/\/cad4security.org\/?page_id=4639"},"modified":"2024-06-03T18:05:28","modified_gmt":"2024-06-03T18:05:28","slug":"riscv-vulnerability-details","status":"publish","type":"page","link":"http:\/\/cad4security.org\/index.php\/riscv-vulnerability-details\/","title":{"rendered":"SoC Vulnerability Database"},"content":{"rendered":"\n

Welcome to the SoC Vulnerability Database Page!<\/p>\n\n\n\n

This effort aims to provide researchers and practitioners from academia and industry with a set of vulnerabilities in SoC (System on Chip) based on security objectives in hardware to perform various experimental analyses. In the future, we are planning to provide a variety of categories that are intended to simplify navigation, browsing, and mapping.<\/p>\n\n\n\n\n

“Please cite the following paper if you use the SoC vulnerability database in your work.”\u00a0<\/strong><\/p>\n\n\n\n

S. Tarek, H. A. Shaikh, S. R. Rajendran and F. Farahmandi, “Benchmarking of SoC-Level Hardware Vulnerabilities: A Complete Walkthrough,” 2023 IEEE Computer Society Annual Symposium on VLSI (ISVLSI)<\/em>, Foz do Iguacu, Brazil, 2023, pp. 1-6, doi: 10.1109\/ISVLSI59464.2023.10238612.<\/a><\/p>\n\n\n\n

\n

Contributors: Shams Tarek, Sree Ranjani Rajendran\u00a0, Mark Tehranipoor, Farimah Farahmandi\u00a0<\/p>\n<\/div>\n\n\n\n\n\n

For any information, please send an email to shams.tarek@ufl.edu.<\/em><\/p>\n\n\n\n\n

SoC Vulnerability #1<\/a><\/h3>\n\"\"<\/a>

CWE-ID: – 1198
\nHardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses, and information leakage.\u00a0\u00a0\u00a0<\/p>\n<\/div>

Read moreSoC Vulnerability #1<\/span><\/a><\/div><\/div><\/article>

SoC Vulnerability #2<\/a><\/h3>\n\"\"<\/a>

CWE-ID: – 266
\nHardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses, and information leakage.\u00a0\u00a0\u00a0<\/p>\n<\/div>

Read moreSoC Vulnerability #2<\/span><\/a><\/div><\/div><\/article>

SoC Vulnerability #3<\/a><\/h3>\n\"\"<\/a>

CWE-ID: – 1198
\nHardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses, and information leakage.\u00a0\u00a0\u00a0<\/p>\n<\/div>

Read moreSoC Vulnerability #3<\/span><\/a><\/div><\/div><\/article>

SoC Vulnerability #4<\/a><\/h3>\n\"\"<\/a>

CWE-ID: – 1272
\nHardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses, and information leakage.\u00a0\u00a0\u00a0<\/p>\n<\/div>

Read moreSoC Vulnerability #4<\/span><\/a><\/div><\/div><\/article>

SoC Vulnerability #5<\/a><\/h3>\n\"\"<\/a>

CWE-ID: – 1262
\nUnauthorized page access request in the memory management unit (MMU)<\/p>\n<\/div>

Read moreSoC Vulnerability #5<\/span><\/a><\/div><\/div><\/article>

SoC Vulnerability #6<\/a><\/h3>\n\"\"<\/a>

CWE-ID: – 1262
\nIllegal Physical Memory Protection (PMP) unit access after mismatch<\/p>\n<\/div>

Read moreSoC Vulnerability #6<\/span><\/a><\/div><\/div><\/article><\/div><\/div>","protected":false},"excerpt":{"rendered":"

Welcome to the SoC Vulnerability Database Page! This effort aims to provide researchers and practitioners from academia and industry with a set of vulnerabilities in SoC (System on Chip) based on security objectives in hardware to perform various experimental analyses. In the future, we are planning to provide a variety of categories that are intended …<\/p>\n","protected":false},"author":10,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"acf":[],"_links":{"self":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/4639"}],"collection":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/comments?post=4639"}],"version-history":[{"count":31,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/4639\/revisions"}],"predecessor-version":[{"id":5294,"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/pages\/4639\/revisions\/5294"}],"wp:attachment":[{"href":"http:\/\/cad4security.org\/index.php\/wp-json\/wp\/v2\/media?parent=4639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}