🚨 [security] Update typeorm 0.3.27 → 1.1.0 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ typeorm (0.3.27 → 1.1.0) · Repo · Changelog

Security Advisories 🚨

🚨 TypeORM: SQL Injection in UpdateQueryBuilder/SoftDeleteQueryBuilder orderBy (MySQL/MariaDB)

Impact

Blind SQL injection vulnerability in UpdateQueryBuilder and SoftDeleteQueryBuilder affecting MySQL and MariaDB users.

UpdateQueryBuilder and SoftDeleteQueryBuilder (including their addOrderBy variants) do not validate the order parameter against an allowlist of permitted values (ASC/DESC). The caller-supplied value is stored verbatim and concatenated directly into the generated SQL string without quoting or parameterization. SelectQueryBuilder.orderBy performs this validation correctly; the affected builders do not.

If any code path passes user-controlled input to orderBy/addOrderBy on an update or soft-delete query, an attacker can inject arbitrary SQL via the sort direction — even when the column name itself is hardcoded.

Demonstrated impact includes:

• Data exfiltration via time-based blind extraction (e.g. using SLEEP() to infer secret values bit by bit)
• Row targeting manipulation in queries using LIMIT patterns
• Denial of service via SLEEP()-based query exhaustion

CVSS 3.1: 8.6 (High) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Affected files (relative to commit 73fda419):

• src/query-builder/UpdateQueryBuilder.ts: lines 383–419 and 718–744
• src/query-builder/SoftDeleteQueryBuilder.ts: lines 352–388 and 520–546

The vulnerability was introduced in commit 03799bd2 (v0.1.12) and is present through the latest release (v0.3.28).

Patches

A fix has been released in 0.3.29 (1b66c44) and 1.0.0 (93eec63).

Workarounds

Applications can manually validate the order argument before passing it to orderBy or addOrderBy on update or soft-delete query builders:

const direction = userInput.toUpperCase();
if (direction !== 'ASC' && direction !== 'DESC') {
  throw new Error('Invalid sort direction');
}
qb.orderBy(column, direction as 'ASC' | 'DESC');

Do not pass user-controlled values to orderBy/addOrderBy on UpdateQueryBuilder or SoftDeleteQueryBuilder without this validation.

References

• Introduced in commit 03799bd (v0.1.12)
• Confirmed present in v0.3.28 (commit 73fda41)
• See SelectQueryBuilder.orderBy for the correct validation pattern this fix should mirror

Release Notes

1.1.0

More info than we can show here.

1.0.0

More info than we can show here.

0.3.30

More info than we can show here.

0.3.29

More info than we can show here.

0.3.28

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ dayjs (indirect, 1.11.19 → 1.11.21) · Repo · Changelog

Release Notes

1.11.21

More info than we can show here.

1.11.20

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ dedent (indirect, 1.7.0 → 1.7.2) · Repo · Changelog

Release Notes

1.7.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ picomatch (indirect, 4.0.3 → 4.0.5) · Repo · Changelog

Security Advisories 🚨

🚨 Picomatch has a ReDoS vulnerability via extglob quantifiers

Impact

picomatch is vulnerable to Regular Expression Denial of Service (ReDoS) when processing crafted extglob patterns. Certain patterns using extglob quantifiers such as +() and *(), especially when combined with overlapping alternatives or nested extglobs, are compiled into regular expressions that can exhibit catastrophic backtracking on non-matching input.

Examples of problematic patterns include +(a|aa), +(*|?), +(+(a)), *(+(a)), and +(+(+(a))). In local reproduction, these patterns caused multi-second event-loop blocking with relatively short inputs. For example, +(a|aa) compiled to ^(?:(?=.)(?:a|aa)+)$ and took about 2 seconds to reject a 41-character non-matching input, while nested patterns such as +(+(a)) and *(+(a)) took around 29 seconds to reject a 33-character input on a modern M1 MacBook.

Applications are impacted when they allow untrusted users to supply glob patterns that are passed to picomatch for compilation or matching. In those cases, an attacker can cause excessive CPU consumption and block the Node.js event loop, resulting in a denial of service. Applications that only use trusted, developer-controlled glob patterns are much less likely to be exposed in a security-relevant way.

Patches

This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2.

Users should upgrade to one of these versions or later, depending on their supported release line.

Workarounds

If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch.

Possible mitigations include:

• disable extglob support for untrusted patterns by using noextglob: true
• reject or sanitize patterns containing nested extglobs or extglob quantifiers such as +() and *()
• enforce strict allowlists for accepted pattern syntax
• run matching in an isolated worker or separate process with time and resource limits
• apply application-level request throttling and input validation for any endpoint that accepts glob patterns

Resources

• Picomatch repository: https://github.com/micromatch/picomatch
• lib/parse.js and lib/constants.js are involved in generating the vulnerable regex forms
• Comparable ReDoS precedent: CVE-2024-4067 (micromatch)
• Comparable generated-regex precedent: CVE-2024-45296 (path-to-regexp)

🚨 Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching

Impact

picomatch is vulnerable to a method injection vulnerability (CWE-1321) affecting the POSIX_REGEX_SOURCE object. Because the object inherits from Object.prototype, specially crafted POSIX bracket expressions (e.g., [[:constructor:]]) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression.

This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control.

All users of affected picomatch versions that process untrusted or user-controlled glob patterns are potentially impacted.

Patches

This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2.

Users should upgrade to one of these versions or later, depending on their supported release line.

Workarounds

If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch.

Possible mitigations include:

• Sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like [[:...:]].

• Avoiding the use of POSIX bracket expressions if user input is involved.

• Manually patching the library by modifying POSIX_REGEX_SOURCE to use a null prototype:

  const POSIX_REGEX_SOURCE = {
    __proto__: null,
    alnum: 'a-zA-Z0-9',
    alpha: 'a-zA-Z',
    // ... rest unchanged
  };

Resources

• fix for similar issue: #144
• picomatch repository https://github.com/micromatch/picomatch

Release Notes

4.0.5

More info than we can show here.

4.0.4

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tinyglobby (indirect, 0.2.15 → 0.2.17) · Repo · Changelog

Release Notes

0.2.17

More info than we can show here.

0.2.16

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 get-east-asian-width (added, 1.6.0)

🆕 emoji-regex (added, 10.6.0)

🆕 string-width (added, 7.2.0)

🆕 wrap-ansi (added, 9.0.2)

🆕 cliui (added, 9.0.1)

🆕 yargs (added, 18.0.0)

🆕 yargs-parser (added, 22.0.0)

🗑️ app-root-path (removed)

🗑️ available-typed-arrays (removed)

🗑️ call-bind (removed)

🗑️ define-data-property (removed)

🗑️ for-each (removed)

🗑️ has-property-descriptors (removed)

🗑️ is-callable (removed)

🗑️ is-typed-array (removed)

🗑️ isarray (removed)

🗑️ possible-typed-array-names (removed)

🗑️ set-function-length (removed)

🗑️ sha.js (removed)

🗑️ to-buffer (removed)

🗑️ typed-array-buffer (removed)

🗑️ which-typed-array (removed)

🗑️ buffer (removed)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.