human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "spoiler speculative load hazards boost rowhammer and cache attacks"
  Abstract: Modern microarchitectures incorporate optimization techniques such as speculative loads and store forwarding to improve the memory bottleneck. The processor executes the load speculatively before the stores, and forwards the data of a preceding store to the load if there is a potential dependency. This enhances performance since the load does not have to wait for preceding stores to complete. However, the dependency prediction relies on partial address information, which may lead to false dependencies and stall hazards. #R##N#In this work, we are the first to show that the dependency resolution logic that serves the speculative load can be exploited to gain information about the physical page mappings. Microarchitectural side-channel attacks such as Rowhammer and cache attacks like Prime+Probe rely on the reverse engineering of the virtual-to-physical address mapping. We propose the SPOILER attack which exploits this leakage to speed up this reverse engineering by a factor of 256. Then, we show how this can improve the Prime+Probe attack by a 4096 factor speed up of the eviction set search, even from sandboxed environments like JavaScript. Finally, we improve the Rowhammer attack by showing how SPOILER helps to conduct DRAM row conflicts deterministically with up to 100% chance, and by demonstrating a double-sided Rowhammer attack with normal user's privilege. The later is due to the possibility of detecting contiguous memory pages using the SPOILER leakage.

Connected through hyperedge HE-1 (induced by source paper "are we susceptible to rowhammer an end to end methodology for cloud providers"):
  with members:
    - "rowhammer a retrospective"
    - "nethammer inducing rowhammer faults through network requests"
    - "pointing in the right direction securing memory accesses in a faulty world"
    - "another flip in the wall of rowhammer defenses"
    - "the rowhammer problem and other issues we may face as memory becomes denser"
    - "can t touch this practical and generic software only defenses against rowhammer attacks"
    - "rowhammer js a remote software induced fault attack in javascript"
    - "drama exploiting dram addressing for cross cpu attacks"

Connected through hyperedge HE-2 (induced by source paper "specusym speculative symbolic execution for cache timing leak detection"):
  with members:
    - "mitigating power side channels during compilation"
    - "specfuzz bringing spectre type vulnerabilities to the surface"
    - "identifying cache based side channels through secret augmented abstract interpretation"
    - "neural network model extraction attacks in edge devices by hearing architectural hints"
    - "abstract interpretation under speculative execution"
    - "ct fuzz fuzzing for timing leaks"
    - "savior towards bug driven hybrid testing"
    - "kleespectre detecting information leakage through speculative cache attacks via symbolic execution"

Connected through hyperedge HE-3 (induced by source paper "store to leak forwarding leaking data on meltdown resistant cpus"):
  with members:
    - "practical enclave malware with intel sgx"
    - "smotherspectre exploiting speculative execution through port contention"
    - "page cache attacks"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-4 (induced by source paper "zombieload cross privilege boundary data sampling"):
  with members:
    - "smotherspectre exploiting speculative execution through port contention"
    - "fallout reading kernel writes from user space"
    - "store to leak forwarding leaking data on meltdown resistant cpus"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "spectector principled detection of speculative information flows"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"

Connected through hyperedge HE-5 (induced by source paper "revisiting and evaluating software side channel vulnerabilities and countermeasures in cryptographic applications"):
  with members:
    - "when human cognitive modeling meets pins user independent inter keystroke timing attacks"
    - "identifying cache based side channels through secret augmented abstract interpretation"
    - "sgxpectre stealing intel secrets from sgx enclaves via speculative execution"
    - "meltdownprime and spectreprime automatically synthesized attacks exploiting invalidation based coherence protocols"
    - "verifying and synthesizing constant resource implementations with types"
    - "spectre attacks exploiting speculative execution"
    - "robust website fingerprinting through the cache occupancy channel"
    - "a systematic evaluation of transient execution attacks and defenses"

Connected through hyperedge HE-6 (induced by source paper "towards constant time foundations for the new spectre era"):
  with members:
    - "abstract interpretation under speculative execution"
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "store to leak forwarding leaking data on meltdown resistant cpus"
    - "zombieload cross privilege boundary data sampling"
    - "inspectre breaking and fixing microarchitectural vulnerabilities by formal analysis"
    - "eliminating timing side channel leaks using program repair"
    - "speculative buffer overflows attacks and defenses"
    - "spectector principled detection of speculative information flows"

Connected through hyperedge HE-7 (induced by source paper "fallout reading kernel writes from user space"):
  with members:
    - "spectre is here to stay an analysis of side channels and speculative execution"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "spectre attacks exploiting speculative execution"
    - "spectre returns speculation attacks using the return stack buffer"
    - "ret2spec speculative execution using return stack buffers"
    - "a systematic evaluation of transient execution attacks and defenses"
    - "lazyfp leaking fpu register state using microarchitectural side channels"

Connected through hyperedge HE-8 (induced by source paper "a systematic evaluation of transient execution attacks and defenses"):
  with members:
    - "smotherspectre exploiting speculative execution through port contention"
    - "speculative buffer overflows attacks and defenses"
    - "netspectre read arbitrary memory over network"
    - "safespec banishing the spectre of a meltdown with leakage free speculation"
    - "spectector principled detection of speculative information flows"
    - "spectre attacks exploiting speculative execution"
    - "you shall not bypass employing data dependencies to prevent bounds check bypass"
    - "spectre returns speculation attacks using the return stack buffer"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.CR(Cryptography and Security)