Feng Xiao

The issue arises from the `gitCommitInfo()` method failing to sanitize its `commit` parameter, which later flows into a sensitive command execution API. This allows attackers to inject malicious commands once they control the hash content, potentially leading to command injection attacks. The vulnerability enables attackers to inject arguments to the git binary.

The issue is related to Arbitrary Code Execution due to improper sanitization of the `getProcessByName` function. This allows for potential code execution without proper validation.

The issue concerns Arbitrary Command Execution via the `kill` function due to missing sanitization of the `port` argument. This allows for potential exploitation. No information is provided about the estimated number of affected devices or real-world incidents.

The issue is related to Arbitrary Command Injection due to the `fetchRepo` API missing sanitization of the `href` field of external input. This allows for potential command injection attacks.

The gatsby-plugin-mdx plugin is vulnerable to Deserialization of Untrusted Data when passing input through to the `gray-matter` package, due to its default configurations that are missing input sanitization. This vulnerability can be exploited when passing input in both webpack (MDX files in `src/pages` or MDX file imported as a component in frontend / React code) and data mode (querying MDX nodes via GraphQL). The injected JavaScript executes in the context of the build server. To exploit this vulnerability, untrusted/unsanitized input would need to be sourced or added into an MDX file.

The issue concerns the post-loader package, which is a webpack loader for blog posts written in Markdown. It is vulnerable to Arbitrary Code Execution due to the use of a markdown parser in an unsafe way. This allows any JavaScript code inside the markdown input files to be evaluated and executed.

The issue concerns Prototype Pollution via the object-extend package. No information is provided about the estimated number of potentially affected devices worldwide or real-world incidents where this issue was exploited.

The issue is caused by incorrect parsing of certain JSON input, which may result in js-bson not correctly serializing BSON. This can cause unexpected application behavior, including data disclosure.

The issue allows Internal Property Tampering. A maliciously crafted JavaScript object can bypass several inspection functions provided by valib. Valib uses a built-in function (hasOwnProperty) from the unsafe user-input to examine an object. It is possible for a crafted payload to overwrite this function to manipulate the inspection results to bypass security checks.

The issue allows attackers to forge adding additional properties into user-input processed by taffy, which can allow access to any data items in the DB. Taffy sets an internal index for each data item in its DB. However, it is found that the internal index can be forged by adding additional properties into user-input. If an index is found in the query, taffyDB will ignore other query conditions and directly return the indexed data item. Moreover, the internal index is in an easily-guessable format, such as `T000002R000001`. As such, attackers can use this vulnerability to access any data items in the DB.

A maliciously crafted JavaScript object can bypass the `sanitize()` and the `validate()` functions used within schema-inspector.