TLP: Clear - The repository of the DevGuard Web Project

👩‍💻 DevGuard Web

0.12.1 fix-api-url

main

0.12.3

0.13.2

0.14.2 add-page-prop-to-RiskAssessmentFeed

0.13.11 client-side-data-fetching

0.13.15

0.13.3

0.15.3

0.15.0

0.13.10 fix-asset-api-in-component-path

feature-delte-artifact

0.13.12 add-dynamic-github-app-url

0.14.3

0.14.1

0.13.6

0.13.4

0.15.2

0.13.0

0.13.7 fix-updated-pat

0.13.17

0.13.9

0.12.0 fix-dependencies-sorting

0.13.16

0.13.5

0.13.18

0.13.14 190-dependency-table-dialog-with-graph

add-devguard-api-url-to-autosetup

0.15.1 634--button-to-delete-an-organization

 TLP: Clear - Devguard GitLab CI/CD Components

🧩 DevGuard CI-Components

TLP: Clear - DevGuard GitHub Reusable Workflows

🧩 DevGuard Action

TLP: Clear - The documentation for the DevGuard Project

📚 DevGuard Documentation

TLP: Clear - The repository for the customized DevGuard Postgresql

🗄️ Devguard Postgresql

TLP: Clear - The main repository - contains the API, the devguard-scanner CLI and the Helm-Chart

💡 DevGuard

TLP: Clear - Manage your CVEs seamlessly, Integrate your Vulnerability Scanners, Documentation made easy, Compliance to security Frameworks - OWASP Incubating Project

🛡️ DevGuard

Robot User

Badge-API

Test Project 1

Lars Hermges

Patrick Rissmann

Sebastian Kawelke

Tim Bastin

David Luhmer

Refaei Shikho

Frédéric Noppe

timbastin

seb-kw

Frederic-Kenji

refoo0

L3montree Cybersecurity

Webhook which sends notification into our matrix chat

Matrix Error-Tracking

Issue summary: A timing side-channel which could potentially allow recovering
the private key exists in the ECDSA signature computation.

Impact summary: A timing side-channel in ECDSA signature computations
could allow recovering the private key by an attacker. However, measuring
the timing would require either local access to the signing application or
a very fast network connection with low latency.

There is a timing signal of around 300 nanoseconds when the top word of
the inverted ECDSA nonce value is zero. This can happen with significant
probability only for some of the supported elliptic curves. In particular
the NIST P-521 curve is affected. To be able to measure this leak, the attacker
process must either be located in the same physical computer or must
have a very fast network connection with low latency. For that reason
the severity of this vulnerability is Low.

The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.

Next.js is a React framework for building full-stack web applications. In versions starting from 13.0 to before 14.2.30 and 15.0.0 to before 15.2.2, Next.js may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active. This issue has been patched in versions 14.2.30 and 15.2.2.

Next.js is a React framework for building full-stack web applications. In versions before 14.2.31 and from 15.0.0 to before 15.4.5, Next.js Image Optimization API routes are affected by cache key confusion. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug. This vulnerability has been fixed in Next.js versions 14.2.31 and 15.4.5. All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.

Next.js is a React framework for building full-stack web applications. In versions before 14.2.31 and from 15.0.0 to before 15.4.5, Next.js Image Optimization is vulnerable to content injection. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery. This vulnerability has been fixed in Next.js versions 14.2.31 and 15.4.5.

Next.js is a React framework for building full-stack web applications. Prior to versions 14.2.32 and 15.4.7, when next() was used without explicitly passing the request object, it could lead to SSRF in self-hosted applications that incorrectly forwarded user-supplied headers. This vulnerability has been fixed in Next.js versions 14.2.32 and 15.4.7. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.

Babel is a compiler for writing next generation JavaScript. When using versions of Babel prior to 7.26.10 and 8.0.0-alpha.17 to compile regular expression named capturing groups, Babel will generate a polyfill for the `.replace` method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to `.replace`). Generated code is vulnerable if all the following conditions are true: Using Babel to compile regular expression named capturing groups, using the `.replace` method on a regular expression that contains named capturing groups, and the code using untrusted strings as the second argument of `.replace`. This problem has been fixed in `@babel/helpers` and `@babel/runtime` 7.26.10 and 8.0.0-alpha.17. It's likely that individual users do not directly depend on `@babel/helpers`, and instead depend on `@babel/core` (which itself depends on `@babel/helpers`). Upgrading to `@babel/core` 7.26.10 is not required, but it guarantees use of a new enough `@babel/helpers` version. Note that just updating Babel dependencies is not enough; one will also need to re-compile the code. No known workarounds are available.

**DISPUTED**A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.

The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting in 
controlled loss of availability. An attacker who can exploit a buffer 
overflow without triggering the stack-protector might be able to change 
program flow control to cause an uncontrolled loss of availability or to
 go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.

Prism (aka PrismJS) through 1.29.0 allows DOM Clobbering (with resultant XSS for untrusted input that contains HTML but does not directly contain JavaScript), because document.currentScript lookup can be shadowed by attacker-injected HTML elements.

A vulnerability was found in juliangruber brace-expansion up to 1.1.11/2.0.1/3.0.0/4.0.0. It has been rated as problematic. Affected by this issue is the function expand of the file index.js. The manipulation leads to inefficient regular expression complexity. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 1.1.12, 2.0.2, 3.0.1 and 4.0.1 is able to address this issue. The name of the patch is a5b98a4f30d7813266b221435e1eaaf25a1b0ac5. It is recommended to upgrade the affected component.

Package	Max Risk	Max CVSS	Vulnerability Count	Installed Version	Action
debian/openssl	LOW (2.4)	MEDIUM (4.1)	1	3.0.15	No fix available
next	LOW (3.8)	MEDIUM (6.5)	8	14.2.26	Update to version 14.2.32 to reduce total risk by 20.1
@babel/runtime	LOW (3.6)	MEDIUM (6.2)	1	7.22.5	Update to version 7.26.10 to reduce total risk by 3.6
debian/gcc-12	LOW (2.6)	MEDIUM (4.8)	1	12.2.0	No fix available
prismjs	LOW (1.4)	MEDIUM (4.9)	2	1.27.0	Update to version 1.30.0 to reduce total risk by 2.8
brace-expansion	LOW (0.1)	LOW (2.3)	2	1.1.11	Update to version 1.1.12 to reduce total risk by 0.3
brace-expansion	LOW (0.1)	LOW (2.3)	2	2.0.1	Update to version 2.0.2 to reduce total risk by 0.1

🛡️ DevGuard
Group
/👩‍💻 DevGuard Web
Repository

Identified Risks