<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 07 Jun 2026 08:11:10 +0000</lastBuildDate>
    <item>
      <title>e88925a4-b206-4d7f-bd0e-c29d91809b9d</title>
      <link>https://db.gcve.eu/sighting/e88925a4-b206-4d7f-bd0e-c29d91809b9d/export</link>
      <description>{"uuid": "e88925a4-b206-4d7f-bd0e-c29d91809b9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42018", "type": "seen", "source": "https://t.me/cvedetector/7716", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42018 - Atos Eviden SMC xScale Privilege Escalation\", \n  \"Content\": \"CVE ID : CVE-2024-42018 \nPublished : Oct. 11, 2024, 5:15 p.m. | 16\u00a0minutes ago \nDescription : An issue was discovered in Atos Eviden SMC xScale before 1.6.6. During initialization of nodes, some configuration parameters are retrieved from management nodes. These parameters embed credentials whose integrity and confidentiality may be important to the security of the HPC configuration. Because these parameters are needed for initialization, there is no available mechanism to ensure access control on the management node, and a mitigation measure is normally put in place to prevent access to unprivileged users. It was discovered that this mitigation measure does not survive a reboot of diskful nodes. (Diskless nodes are not at risk.) The mistake lies in the cloudinit configuration: the iptables configuration should have been in the bootcmd instead of the runcmd section. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-11T19:33:29.000000Z"}</description>
      <content:encoded>{"uuid": "e88925a4-b206-4d7f-bd0e-c29d91809b9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42018", "type": "seen", "source": "https://t.me/cvedetector/7716", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42018 - Atos Eviden SMC xScale Privilege Escalation\", \n  \"Content\": \"CVE ID : CVE-2024-42018 \nPublished : Oct. 11, 2024, 5:15 p.m. | 16\u00a0minutes ago \nDescription : An issue was discovered in Atos Eviden SMC xScale before 1.6.6. During initialization of nodes, some configuration parameters are retrieved from management nodes. These parameters embed credentials whose integrity and confidentiality may be important to the security of the HPC configuration. Because these parameters are needed for initialization, there is no available mechanism to ensure access control on the management node, and a mitigation measure is normally put in place to prevent access to unprivileged users. It was discovered that this mitigation measure does not survive a reboot of diskful nodes. (Diskless nodes are not at risk.) The mistake lies in the cloudinit configuration: the iptables configuration should have been in the bootcmd instead of the runcmd section. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-11T19:33:29.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/e88925a4-b206-4d7f-bd0e-c29d91809b9d/export</guid>
      <pubDate>Fri, 11 Oct 2024 19:33:29 +0000</pubDate>
    </item>
  </channel>
</rss>
