Research on Arm TrustZone and Understanding the Security Vulnerability in Its Cache Architecture

With virtual assistants, both changes and serious conveniences are provided in human life. For this reason, the use of virtual assistants is increasing. The virtual assistant software has started to be produced as separate devices as well as working on phones, tablets, and computer systems. Google Home is one of these devices. Google Home can work integrated with smart home systems and various Internet of Things devices. The security of these systems is an important issue. As a result of attackers taking over these systems, very serious problems may occur. It is very important to take the necessary actions to detect these problems and to take the necessary measures to prevent possible attacks. The purpose of this study is to test whether an attack that attackers can make to these systems via network time protocol will be successful or not. Accordingly, it has been tried to attack the wireless connection established between Google Home and an Internet of Things device over the network time protocol. Attack results have been shared.

Download Full-text

Monolithic 3D-Based SRAM/MRAM Hybrid Memory for an Energy-Efficient Unified L2 TLB-Cache Architecture

IEEE Access ◽

10.1109/access.2021.3054021 ◽

2021 ◽

Vol 9 ◽

pp. 18915-18926

Author(s):

Young-Ho Gong

Keyword(s):

Energy Efficient ◽

Hybrid Memory ◽

Cache Architecture

Download Full-text

Change Point Problem in Security Vulnerability Discovery Model

2019 International Conference on Software Security and Assurance (ICSSA) ◽

10.1109/icssa48308.2019.00010 ◽

2019 ◽

Author(s):

Ankur Shukla ◽

Basel Katt

Keyword(s):

Change Point ◽

Point Problem ◽

Security Vulnerability ◽

Change Point Problem ◽

Vulnerability Discovery

Download Full-text

Lags in the release, adoption, and propagation of npm vulnerability fixes

Empirical Software Engineering ◽

10.1007/s10664-021-09951-x ◽

2021 ◽

Vol 26 (3) ◽

Author(s):

Bodin Chinthanet ◽

Raula Gaikovina Kula ◽

Shane McIntosh ◽

Takashi Ishio ◽

Akinori Ihara ◽

...

Keyword(s):

Empirical Study ◽

Empirical Investigation ◽

Third Party ◽

Future Research ◽

Software Ecosystem ◽

Security Vulnerability ◽

Preliminary Study ◽

Client Side

AbstractSecurity vulnerability in third-party dependencies is a growing concern not only for developers of the affected software, but for the risks it poses to an entire software ecosystem, e.g., Heartbleed vulnerability. Recent studies show that developers are slow to respond to the threat of vulnerability, sometimes taking four to eleven months to act. To ensure quick adoption and propagation of a release that contains the fix (fixing release), we conduct an empirical investigation to identify lags that may occur between the vulnerable release and its fixing release (package-side fixing release). Through a preliminary study of 231 package-side fixing release of npm projects on GitHub, we observe that a fixing release is rarely released on its own, with up to 85.72% of the bundled commits being unrelated to a fix. We then compare the package-side fixing release with changes on a client-side (client-side fixing release). Through an empirical study of the adoption and propagation tendencies of 1,290 package-side fixing releases that impact throughout a network of 1,553,325 releases of npm packages, we find that stale clients require additional migration effort, even if the package-side fixing release was quick (i.e., package-side fixing releasetypeSpatch). Furthermore, we show the influence of factors such as the branch that the package-side fixing release lands on and the severity of vulnerability on its propagation. In addition to these lags we identify and characterize, this paper lays the groundwork for future research on how to mitigate propagation lags in an ecosystem.

Download Full-text