<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-22T07:06:03.748552+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-5vwr-qchf-q4pf</id>
    <title>GHSA-5vwr-qchf-q4pf — @cyclonedx/cdxgen: Maven project scanning may allow shell command injection through repository-controlled module paths</title>
    <updated>2026-10-22T07:06:03.750362+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @cyclonedx/cdxgen</p>
<p>## Summary</p>
<p>A command injection vulnerability existed in the Maven scanning flow of cdxgen before version 12.4.3.</p>
<p>When cdxgen scanned an attacker-controlled Maven project, repository-controlled paths could be used in the Maven command construction. In affected versions, some Maven invocations were executed with `shell: true`. A directory name containing shell metacharacters could therefore be interpreted by the shell instead of being treated only as a filesystem path.</p>
<p>This could allow an attacker who controls a scanned repository to execute commands in the cdxgen process context.</p>
<p>The issue affected both the CLI and server mode. The issue is patched in `12.4.3`.</p>
<p>## Affected asset</p>
<p>- Project: cdxgen
- Tested version: 12.4.1
- Mode tested: server mode
- Endpoint: `POST /sbom`
- Scanner path: Java / Maven project scanning</p>
<p>## Patch</p>
<p>Version 12.4.3 includes hardening for this issue with PR #4059</p>
<p>The patch adds multiple mitigations:</p>
<p>- Maven command invocations no longer use unconditional shell execution on POSIX platforms.
- Bazel command invocation was similarly changed away from unconditional shell execution.
- Windows compatibility is preserved using `shell: isWin` where needed.
- `safeSpawnSync` now blocks `shell: true` invocations when the command or direct argument values contain shell metacharacters.
- cdxgen does not validate or sanitise every nested directory. The threat model is updated to clarify mitigation scope.</p>
<p>## Workarounds</p>
<p>The recommended remediation is t…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-5vwr-qchf-q4pf"/>
  </entry>
</feed>
