🚨 [security] Update postcss 8.4.31 → 8.5.14 (minor)

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

---

🚨 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 update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ postcss (8.4.31 → 8.5.14) · Repo · Changelog

Security Advisories 🚨

🚨 PostCSS has XSS via Unescaped </style> in its CSS Stringify Output

PostCSS: XSS via Unescaped </style> in CSS Stringify Output

Summary

PostCSS v8.5.5 (latest) does not escape </style> sequences when stringifying CSS ASTs. When user-submitted CSS is parsed and re-stringified for embedding in HTML <style> tags, </style> in CSS values breaks out of the style context, enabling XSS.

Proof of Concept

const postcss = require('postcss');
// Parse user CSS and re-stringify for page embedding

const userCSS = 'body { content: "</style><script>alert(1)</script><style>"; }';

const ast = postcss.parse(userCSS);

const output = ast.toResult().css;

const html = &lt;style&gt;<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">output</span><span class="pl-kos">}</span></span>&lt;/style&gt;;
console.log(html);

// <style>body { content: "</style><script>alert(1)</script><style>"; }</style>

//

// Browser: </style> closes the style tag, <script> executes

Tested output (Node.js v22, postcss v8.5.5):

Input: body { content: "</style><script>alert(1)</script><style>"; }
Output: body { content: "</style><script>alert(1)</script><style>"; }
Contains </style>: true

Impact

Impact non-bundler use cases since bundlers for XSS on their own. Requires some PostCSS plugin to have malware code, which can inject XSS to website.

Suggested Fix

Escape </style in all stringified output values:

output = output.replace(/<\/(style)/gi, '<\\/$1');

Credits

Discovered and reported by Sunil Kumar (@TharVid)

Release Notes

Too many releases to show here. View the full release notes.

Commits

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

↗️ nanoid (indirect, 3.3.6 → 3.3.12) · Repo · Changelog

Security Advisories 🚨

🚨 Predictable results in nanoid generation when given non-integer values

When nanoid is called with a fractional value, there were a number of undesirable effects:

1. in browser and non-secure, the code infinite loops on while (size--)
2. in node, the value of poolOffset becomes fractional, causing calls to nanoid to return zeroes until the pool is next filled
3. if the first call in node is a fractional argument, the initial buffer allocation fails with an error

Version 3.3.8 and 5.0.9 are fixed.

Release Notes

3.3.12

• Fixed breaking Nano ID by requesting big ID.

3.3.11

• Fixed React Native support.

3.3.8 (from changelog)

• Fixed a way to break Nano ID by passing non-integer size (by @myndzi).

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

Commits

See the full diff on Github. The new version differs by 21 commits:

• Release 3.3.12 version
• Backport fix to CommonJS version too
• Update test
• Backport pool breaking fix
• Fix CI
• Release 3.3.11 version
• Fix CI
• Fix RN support
• Move to manually ESM/CJS dual package
• Release 3.3.10 version
• Fix Expo support
• Release 3.3.9 version
• Remove dev file from npm package
• Release 3.3.8 version
• Update size limit
• Fix pool pollution, infinite loop (#510)
• Release 3.3.7 version
• Update dual-publish
• Remove benchmark from CI for v3
• Fix CI for v3
• Move to pnpm 8

↗️ picocolors (indirect, 1.0.0 → 1.1.1) · Repo · Changelog

Release Notes

1.1.1

What's new?

• Moved TypeScript declarations to a d.ts file #82
• Reworked color detection algorithm to properly work with empty strings in NO_COLOR and FORCE_COLOR env variables #87
• Eliminated require() call to make the package compatible with some tools #87

1.1.0

What's new?

• Added bright color variants #55

1.0.1

What's new?

• Updated color detection mechanism to work properly on Vercel Edge Runtime #64
• Remove use of recursion to avoid possible stack overflow for very long inputs #56

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

Commits

See the full diff on Github. The new version differs by 16 commits:

• picocolors@1.1.1
• Add chalk v5 and yoctocolors to benchmarks (#88)
• Rework color detection (#87)
• fix: usage of `node12` in `testing.yaml` (#73)
• Use mitata, esbuild for benchmarking speed and size (#86)
• fix(types): move types declaration into "real" types declaration file (.d.ts) (#82)
• picocolors@1.1.0
• test: add test (shouldn't overflow when coloring already colored large text) (#74)
• feat: bright colors variants (#55)
• misc
• v1.0.1
• fix: iteratively replace "close" to avoid maximum stack error (#64)
• Fix color detection in edge runtime (#56)
• uniform api usage in complex benchmark
• update benchmarks per recent job run
• Create .gitignore (#37)

↗️ source-map-js (indirect, 1.0.2 → 1.2.1) · Repo · Changelog

Release Notes

1.2.1

• Fix TS2306 “not a module” errors in type definitions (#16) @andersk

• Ensure null source is respected (#26) @dragomirtitian

• Improve ts declarations to be null-safe (#27) @dragomirtitian

1.2.0

Allow to pass options to SourceMapGenerator using SourceMapGenerator.fromSourceMap as second argument

var generator = sourceMap.SourceMapGenerator.fromSourceMap(new SourceMapConsumer(), {
  ignoreInvalidMapping: true,
});

• Add generator options to fromSourceMap (#22) @ai

1.1.0

Add ignoreInvalidMapping option to SourceMapGenerator. If enabled, source-map-js will not throw an error on the incorrect previous source map. Instead, it will print warnings and ignore broken mappings.

var generator = new sourceMap.SourceMapGenerator({
  file: "my-generated-javascript-file.js",
  sourceRoot: "http://example.com/app/js/",
  ignoreInvalidMapping: true,
});

• Do not throw an error since broken prev map is popular issue #20 (#20) @ai
• Add ignoreInvalidMapping option (#21) @7rulnik

1.0.3

• Use sourceContents when non-null, even if it's an empty string (#17) @bshepherdson

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

Commits

See the full diff on Github. The new version differs by 16 commits:

• 1.2.1
• Update changelog
• Improve ts declarations (#27)
• Ensure null source is respected. (#26)
• Fix TS2306 “not a module” errors in type definitions (#16)
• 1.2.0
• Update changelog
• Fix typo
• Add generator options to fromSourceMap (#22)
• 1.1.0
• Add ignoreInvalidMapping option (#21)
• Do not throw an error since broken prev map is popular issue (#20)
• Update CHANGELOG.md
• 1.0.3
• Update changelog
• Use sourceContents when non-null, even if it's an empty string (#17)

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

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)

[depfu]

Closed in favor of #9.