Bump SixLabors.ImageSharp from 1.0.4 to 2.1.9 in /PdfSharpCore
Bumps SixLabors.ImageSharp from 1.0.4 to 2.1.9.
Release notes
Sourced from SixLabors.ImageSharp's releases.
v2.1.9
What's Changed
- [2.1] Fix overflow in MemoryAllocator.Create(options) by
@antonfirsovin SixLabors/ImageSharp#2732- Backport GIF LZW fix to 2.1 by
@antonfirsovin SixLabors/ImageSharp#2756- Backport 2759 to 2.1.x by
@antonfirsovin SixLabors/ImageSharp#2770Full Changelog: https://github.com/SixLabors/ImageSharp/compare/v2.1.8...v2.1.9
v2.1.8
What's Changed
- V2 - Limit Read Palette Indices by
@JimBobSquarePantsin SixLabors/ImageSharp#2719- V2 - Clear Pixel Buffers on Decode. by
@JimBobSquarePantsin SixLabors/ImageSharp#2717- V2 - Limit all memory allocations in the MemoryAllocator layer by
@JimBobSquarePantsin SixLabors/ImageSharp#2715Full Changelog: https://github.com/SixLabors/ImageSharp/compare/v2.1.7...v2.1.8
v2.1.7
What's Changed
- [release/2.1] Disallow allocation attempts of unrepresentable sizes by
@antonfirsovin SixLabors/ImageSharp#2553- [release/2.1] Tiff decoding robustness improvements (#2550) by
@antonfirsovin SixLabors/ImageSharp#2554- [release/2.1] PBM decoder robustness improvements and BufferedReadStream observability by
@antonfirsovin SixLabors/ImageSharp#2555- Backport 2681 by
@JimBobSquarePantsin SixLabors/ImageSharp#2688Full Changelog: https://github.com/SixLabors/ImageSharp/compare/v2.1.6...v2.1.7
v2.1.6
What's Changed
- Backport - Handle EOF in Jpeg bit reader when data is bad to prevent DOS attack. by
@JimBobSquarePantsin SixLabors/ImageSharp#2524Full Changelog: https://github.com/SixLabors/ImageSharp/compare/v2.1.5...v2.1.6
v2.1.5
What's Changed
- Backport #2501 by
@JimBobSquarePantsin SixLabors/ImageSharp#2509Full Changelog: https://github.com/SixLabors/ImageSharp/compare/v2.1.4...v2.1.5
v2.1.4
What's Changed
- Backport WebP fix to 2.1 by
@antonfirsovin SixLabors/ImageSharp#2420Full Changelog: https://github.com/SixLabors/ImageSharp/compare/v2.1.3...v2.1.4
v2.1.3
... (truncated)
Commits
9816ca4Merge pull request #2770 from SixLabors/af/backport-2759-2.1.xb33d666handle DecodingMode6b2030bMerge branch 'release/2.1.x' into af/backport-2759-2.1.x8ffad3fIssue2012BadMinCode should decode now1f5bf23skip Issue2758_DecodeWorks3bf8c57manual port of 3.1 gif decoder28c20deClamp JPEG quality estimation results.4b910e7Decode LZW row by rowa1f2879Merge pull request #2756 from SixLabors/af/git-av-2.1898df7fbackport #2749 to 2.1- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
Could this be prioritized? SixLabors.ImageSharp 1.0.4 has a known vulnerability, so I get warnings in my build as it is now.
please
Yes, I am also waiting for this, as I have to fix this vulnerability as well
I think this library is no longer maintained. Switching to the original PdfSharp is probably the best option, its core build no longer depends on System.Drawing.Common.
Note: I suggest updating ImageSharp to 2.1.10, which is the latest 2.x version without known vulnerabilities (as of now). The 3.x version are also fixed, but changed to the Split License, which may invoke problems for some users. Similar to the SixLabors.Fonts dependency; there are no known vulnerabilities, but from 2.x, it also changed the license.