diff --git a/blog/2026-01-22-introducing-docs-blog.md b/blog/2026-01-22-introducing-docs-blog.md index ede9ae77dc..f831cc7547 100644 --- a/blog/2026-01-22-introducing-docs-blog.md +++ b/blog/2026-01-22-introducing-docs-blog.md @@ -14,6 +14,8 @@ of the reference implementation and also had a vast collection of links and tech content, a lot of which was related to the reference implementation. For newcomers, it was somewhat hard to distill the various aspects and goals of SCS though. + + With the end of the funded project, we split the activities into different organizations with distinct goals: diff --git a/blog/2026-01-23-cve-2026-22797.md b/blog/2026-01-23-cve-2026-22797.md index dd40d2f7d3..fc2ed15b7e 100644 --- a/blog/2026-01-23-cve-2026-22797.md +++ b/blog/2026-01-23-cve-2026-22797.md @@ -16,6 +16,8 @@ public. Instead, we have taken the time to sort out the publication place in the the new Docs blog space, as described by the previous blog post. + + ## The vulnerability Keystone is the central Identity and Access Management component in OpenStack. diff --git a/blog/2026-02-17-cve-2026-24708.md b/blog/2026-02-17-cve-2026-24708.md index 3174d1f12e..74097b81fe 100644 --- a/blog/2026-02-17-cve-2026-24708.md +++ b/blog/2026-02-17-cve-2026-24708.md @@ -25,6 +25,8 @@ on the backing image file without an explicit format specifier, opening up the possibility to overwrite files on the host system by writing a malicious QCOW header to a root or ephemeral disk. + + This vulnerability has been assigned [CVE-2026-24708](https://nvd.nist.gov/vuln/detail/CVE-2026-24708). ## Impact on the SCS software ecosystem diff --git a/blog/2026-04-08-cve-2026-33551.md b/blog/2026-04-08-cve-2026-33551.md index fc488375cd..1b02a6af8e 100644 --- a/blog/2026-04-08-cve-2026-33551.md +++ b/blog/2026-04-08-cve-2026-33551.md @@ -20,6 +20,8 @@ giving AppCreds that are _restricted_ or that have limited roles the ability to create EC2 credentials with the full privileges of the user who created the AppCred. + + This issue was reported by Maxence Bornecque from Orange Cyberdefense CERT Vulnerability Intelligence Watch Team and has been assigned [CVE-2026-33551](https://nvd.nist.gov/vuln/detail/CVE-2026-33551). diff --git a/blog/2026-05-10-kernel-root-exploits.md b/blog/2026-05-10-kernel-root-exploits.md index df866b4a5c..cbf246f19b 100644 --- a/blog/2026-05-10-kernel-root-exploits.md +++ b/blog/2026-05-10-kernel-root-exploits.md @@ -19,6 +19,8 @@ particular, normal users must not achieve the system administrator (root) privileges. Where the kernel fails to ensure this, we have a "local root" vulnerability, a Local Privilege Escalation (LPE). + + The Linux kernel is a large and a complex beast. On one hand it has sophisticated mechanisms to get really good performance out of increasingly complex hardware. On the other hand, it comes with a huge variety of device drivers. From time to diff --git a/blog/2026-05-28-keystone.md b/blog/2026-05-28-keystone.md index 225db85c1c..5fbcdf4935 100644 --- a/blog/2026-05-28-keystone.md +++ b/blog/2026-05-28-keystone.md @@ -13,6 +13,8 @@ policies are enforced. These vulnerabilities allow authenticated attackers to bypass security boundaries, impersonate users, and potentially escalate privileges to cloud administrator. + + The core issues are: - **RBAC Policy Bypass (CVE-2026-42999):** An attacker can inject RBAC policy diff --git a/blog/2026-06-16-cve-2026-46448.md b/blog/2026-06-16-cve-2026-46448.md index 85fd4b92a1..d36e188cf5 100644 --- a/blog/2026-06-16-cve-2026-46448.md +++ b/blog/2026-06-16-cve-2026-46448.md @@ -17,6 +17,8 @@ mapped. While the assigned quota is still observed, the vulnerability may cause exhaustion of resources and confusion of the scheduler (placement) state and thus may result in a Denial of Service for certain resource types. + + This issue was reported by Erichen, Institute of Computing Technology, Chinese Academy of Sciences and was subsequently analyzed and handled by Goutham Pacha Ravi, Dan Smith and Sylvain Bauza. It was assigned CVE-2026-46448. diff --git a/docusaurus.config.js b/docusaurus.config.js index 04b7618c07..d66a77d6fa 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -10,10 +10,12 @@ const config = { url: 'https://docs.scs.community', baseUrl: '/', onBrokenLinks: 'warn', - onBrokenMarkdownLinks: 'warn', favicon: 'img/favicon.png', markdown: { - mermaid: true + mermaid: true, + hooks: { + onBrokenMarkdownLinks: 'warn' + } }, organizationName: 'SovereignCloudStack', // Usually your GitHub org/user name. projectName: 'docs', // Usually your repo name. @@ -124,7 +126,18 @@ const config = { id: 'standards', path: 'standards', routeBasePath: 'standards', - sidebarPath: require.resolve('./sidebarsStandards.js') + sidebarPath: require.resolve('./sidebarsStandards.js'), + // The vendored standards content (see getDocs.js) ships a README.md + // that Docusaurus would render at `/standards/` — the same route as our + // own standards/index.md. Skip it; index.md is the page we want there. + // Repeats Docusaurus' default excludes, which this option replaces. + exclude: [ + 'README.md', + '**/_*.{js,jsx,ts,tsx,md,mdx}', + '**/_*/**', + '**/*.test.{js,jsx,ts,tsx}', + '**/__tests__/**' + ] } ], './src/plugins/docusaurus-plugin-matomo-analytics/index.js', diff --git a/mlc_config.json b/mlc_config.json index 149b82f23c..65cf745404 100644 --- a/mlc_config.json +++ b/mlc_config.json @@ -10,6 +10,12 @@ "headers": { "Accept-Encoding": "zstd, br, gzip, deflate" } + }, + { + "urls": ["https://lwn.net"], + "headers": { + "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0 Safari/537.36" + } } ], "aliveStatusCodes": [200, 300]