<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>vulnerability — LowEndSpirit</title>
        <link>https://staging.lowendspirit.com/index.php?p=/</link>
        <pubDate>Mon, 06 Apr 2026 15:22:06 +0000</pubDate>
        <language>en</language>
            <description>vulnerability — LowEndSpirit</description>
    <atom:link href="https://staging.lowendspirit.com/index.php?p=/discussions/tagged/vulnerability/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>YAWV - Jan 2022 edition</title>
        <link>https://staging.lowendspirit.com/index.php?p=/discussion/3690/yawv-jan-2022-edition</link>
        <pubDate>Fri, 07 Jan 2022 15:24:47 +0000</pubDate>
        <category>WordPress</category>
        <dc:creator>vyas</dc:creator>
        <guid isPermaLink="false">3690@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Yet another WordPress vulnerability</p>

<p><a href="https://www.searchenginejournal.com/wordpress-core-vulnerabilities/432042/" rel="nofollow">https://www.searchenginejournal.com/wordpress-core-vulnerabilities/432042/</a></p>

<p>Rather sketchy details on nature of exploit, or the severity of threat.</p>
]]>
        </description>
    </item>
    <item>
        <title>Intel Vulnerability: Hijacking Transient Execution with Load Value Injection</title>
        <link>https://staging.lowendspirit.com/index.php?p=/discussion/774/intel-vulnerability-hijacking-transient-execution-with-load-value-injection</link>
        <pubDate>Wed, 11 Mar 2020 18:01:00 +0000</pubDate>
        <category>Technical</category>
        <dc:creator>souen</dc:creator>
        <guid isPermaLink="false">774@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Another day, another Intel exploit.</p>

<blockquote><div>
  <p>LVI is a new class of transient-execution attacks exploiting microarchitectural flaws in modern processors to inject attacker data into a victim program and steal sensitive data and keys from Intel SGX, a secure vault in Intel processors for your personal data.</p>
  
  <p>LVI turns previous data extraction attacks around, like Meltdown, Foreshadow, ZombieLoad, RIDL and Fallout, and defeats all existing mitigations. Instead of directly leaking data from the victim to the attacker, we proceed in the opposite direction: we smuggle — "inject" — the attacker's data through hidden processor buffers into a victim program and hijack transient execution to acquire sensitive information, such as the victim’s fingerprints or passwords.</p>
  
  <p>[...]</p>
  
  <p>LVI in 4 simple steps:<br />
  1. Poison a hidden processor buffer with attacker values.<br />
  2. Induce a faulting or assisted load in the victim program.<br />
  3. The attacker's value is transiently injected into code gadgets following the faulting load in the victim program.<br />
  4. Side channels may leave secret-dependent traces, before the processor detects the mistake and rolls back all operations.</p>
</div></blockquote>

<p>Source: <a href="https://lviattack.eu/" rel="nofollow">https://lviattack.eu/</a></p>
]]>
        </description>
    </item>
    <item>
        <title>New Intel CPU vulnerability</title>
        <link>https://staging.lowendspirit.com/index.php?p=/discussion/547/new-intel-cpu-vulnerability</link>
        <pubDate>Mon, 27 Jan 2020 19:24:23 +0000</pubDate>
        <category>Technical</category>
        <dc:creator>joepie91</dc:creator>
        <guid isPermaLink="false">547@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Time to reset the "It's been __ days since the last Intel CPU vulnerability" counter!</p>

<blockquote><div>
  <p>We present CacheOut, a new speculative execution attack that is capable of leaking data from Intel CPUs across many security boundaries. We show that despite Intel's attempts to address previous generations of speculative execution attacks, CPUs are still vulnerable, allowing attackers to exploit these vulnerabilities to leak sensitive data.</p>
  
  <p>Moreover, unlike previous MDS issues, we show in our work how an attacker can exploit the CPU's caching mechanisms to select what data to leak, as opposed to waiting for the data to be available. Finally, we empirically demonstrate that CacheOut can violate nearly every hardware-based security domain, leaking data from the OS kernel, co-resident virtual machines, and even SGX enclaves.</p>
</div></blockquote>

<p><a rel="nofollow" href="https://cacheoutattack.com/">Source</a></p>

<p>Microcode updates are supposedly already available. Best update ASAP, if you're running Intel and haven't yet... you know the drill.</p>
]]>
        </description>
    </item>
   </channel>
</rss>
