{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,6,6]],"date-time":"2026-06-06T16:08:03Z","timestamp":1780762083485,"version":"3.54.1"},"reference-count":10,"publisher":"Institute of Electrical and Electronics Engineers (IEEE)","issue":"4","license":[{"start":{"date-parts":[[2024,7,1]],"date-time":"2024-07-01T00:00:00Z","timestamp":1719792000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/ieeexplore.ieee.org\/Xplorehelp\/downloads\/license-information\/USG.html"},{"start":{"date-parts":[[2024,7,1]],"date-time":"2024-07-01T00:00:00Z","timestamp":1719792000000},"content-version":"stm-asf","delay-in-days":0,"URL":"https:\/\/doi.org\/10.15223\/policy-029"},{"start":{"date-parts":[[2024,7,1]],"date-time":"2024-07-01T00:00:00Z","timestamp":1719792000000},"content-version":"stm-asf","delay-in-days":0,"URL":"https:\/\/doi.org\/10.15223\/policy-037"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["IEEE Secur. Privacy"],"published-print":{"date-parts":[[2024,7]]},"DOI":"10.1109\/msec.2024.3409934","type":"journal-article","created":{"date-parts":[[2024,8,2]],"date-time":"2024-08-02T17:45:08Z","timestamp":1722620708000},"page":"18-21","source":"Crossref","is-referenced-by-count":1,"title":["A Viewpoint: A Memory Safety Manifesto"],"prefix":"10.1109","volume":"22","author":[{"ORCID":"https:\/\/orcid.org\/0000-0002-6059-925X","authenticated-orcid":false,"given":"Dan S.","family":"Wallach","sequence":"first","affiliation":[{"name":"Defense Advanced Research Projects Agency’s Information Innovation Office (I2O), Arlington, VA, USA"}],"role":[{"vocabulary":"crossref","role":"author"}]},{"given":"Bob","family":"Lord","sequence":"additional","affiliation":[{"name":"Cybersecurity and Infrastructure Security Agency, USA"}],"role":[{"vocabulary":"crossref","role":"author"}]}],"member":"263","reference":[{"key":"ref1","volume-title":"What is memory safety?","author":"Hicks","year":"2023"},{"key":"ref2","volume-title":"Software memory safety","year":"2023"},{"key":"ref3","volume-title":"The case for memory safe roadmaps","year":"2023"},{"key":"ref4","volume-title":"Future of memory safety: Challenges and recommendations","author":"Grauer","year":"2023"},{"key":"ref5","volume-title":"Memory safe languages in Android 13","author":"Stoep","year":"2023"},{"key":"ref6","volume-title":"Why Discord is switching from Go to Rust","author":"Howarth","year":"2023"},{"key":"ref7","doi-asserted-by":"publisher","DOI":"10.1145\/1646353.1646374"},{"key":"ref8","volume-title":"Expolit mitigations","author":"Polychronakis","year":"2023"},{"issue":"172","key":"ref9","first-page":"8","article-title":"The year of C successor languages","volume":"30","author":"Teodorescu","year":"2022","journal-title":"Overload"},{"key":"ref10","first-page":"699","article-title":"Retrofitting fine grain isolation in the Firefox renderer","volume-title":"Proc. 29th USENIX Conf. Secur. Symp.","author":"Narayan","year":"2020"}],"container-title":["IEEE Security & Privacy"],"original-title":[],"link":[{"URL":"http:\/\/xplorestaging.ieee.org\/ielx8\/8013\/10621858\/10621859.pdf?arnumber=10621859","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2024,8,7]],"date-time":"2024-08-07T18:05:31Z","timestamp":1723053931000},"score":1,"resource":{"primary":{"URL":"https:\/\/ieeexplore.ieee.org\/document\/10621859\/"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2024,7]]},"references-count":10,"journal-issue":{"issue":"4"},"URL":"https:\/\/doi.org\/10.1109\/msec.2024.3409934","relation":{},"ISSN":["1540-7993","1558-4046"],"issn-type":[{"value":"1540-7993","type":"print"},{"value":"1558-4046","type":"electronic"}],"subject":[],"published":{"date-parts":[[2024,7]]}}}