chore(deps): bump @xmldom/xmldom from 0.9.9 to 0.9.10 (#1407)
Bumps @xmldom/xmldom from 0.9.9 to 0.9.10.
Release notes
Sourced from
@xmldom/xmldom's releases.0.9.10
Fixed
- Security:
XMLSerializer.serializeToString()(andNode.toString(),NodeList.toString()) now accept arequireWellFormedoption. When{ requireWellFormed: true }is passed, the serializer throwsInvalidStateErrorfor injection-prone node content, preventing XML injection via attacker-controlled node data.GHSA-j759-j44w-7fr8GHSA-x6wf-f3px-wcqxGHSA-f6ww-3ggp-fr8h
- Comment: throws when
datacontains--anywhere, ends with-, or contains characters outside the XMLCharproduction- ProcessingInstruction: throws when target contains
:or matchesxml(case-insensitive), ordatacontains characters outside the XMLCharproduction or contains?>- DocumentType: throws when
publicIdfailsPubidLiteral,systemIdfailsSystemLiteral, orinternalSubsetcontains]>- Security: DOM traversal operations (
XMLSerializer.serializeToString(),Node.prototype.normalize(),Node.prototype.cloneNode(true),Document.prototype.importNode(node, true),node.textContentgetter,getElementsByTagName()/getElementsByTagNameNS()/getElementsByClassName()/getElementById(),Node.prototype.isEqualNode()) are now iterative. Previously, deeply nested DOM trees would exhaust the JavaScript call stack and throw an unrecoverableRangeError.GHSA-2v35-w6hq-6mfwisEqualNodenow correctly returnsfalsefor CDATASection nodes with differentdataDeprecated
- The
splitCDATASectionsserializer option is deprecated and will be removed in the next breaking release. The automatic splitting of"]]>"inCDATASectiondata was introduced as a workaround; userequireWellFormed: trueor ensureCDATASectiondata does not contain"]]>"before serialization.Chore
- updated dependencies
Thank you,
@Jvr2022,@praveen-kv,@TharVid,@decsecre583,@tlsbollei,@KarimTantawey, for your contributionsChangelog
Sourced from
@xmldom/xmldom's changelog.0.9.10
Fixed
- Security:
XMLSerializer.serializeToString()(andNode.toString(),NodeList.toString()) now accept arequireWellFormedoption. When{ requireWellFormed: true }is passed, the serializer throwsInvalidStateErrorfor injection-prone node content, preventing XML injection via attacker-controlled node data.GHSA-j759-j44w-7fr8GHSA-x6wf-f3px-wcqxGHSA-f6ww-3ggp-fr8h
- Comment: throws when
datacontains--anywhere, ends with-, or contains characters outside the XMLCharproduction- ProcessingInstruction: throws when target contains
:or matchesxml(case-insensitive), ordatacontains characters outside the XMLCharproduction or contains?>- DocumentType: throws when
publicIdfailsPubidLiteral,systemIdfailsSystemLiteral, orinternalSubsetcontains]>- Security: DOM traversal operations (
XMLSerializer.serializeToString(),Node.prototype.normalize(),Node.prototype.cloneNode(true),Document.prototype.importNode(node, true),node.textContentgetter,getElementsByTagName()/getElementsByTagNameNS()/getElementsByClassName()/getElementById(),Node.prototype.isEqualNode()) are now iterative. Previously, deeply nested DOM trees would exhaust the JavaScript call stack and throw an unrecoverableRangeError.GHSA-2v35-w6hq-6mfwisEqualNodenow correctly returnsfalsefor CDATASection nodes with differentdataDeprecated
- The
splitCDATASectionsserializer option is deprecated and will be removed in the next breaking release. The automatic splitting of"]]>"inCDATASectiondata was introduced as a workaround; userequireWellFormed: trueor ensureCDATASectiondata does not contain"]]>"before serialization.Chore
- updated dependencies
Thank you,
@Jvr2022,@praveen-kv,@TharVid,@decsecre583,@tlsbollei,@KarimTantawey, for your contributions0.8.13
Fixed
- Security:
XMLSerializer.serializeToString()(andNode.toString(),NodeList.toString()) now accept arequireWellFormedoption (fourth argument, afterisHtmlandnodeFilter). When{ requireWellFormed: true }is passed, the serializer throwsInvalidStateErrorfor injection-prone node content, preventing XML injection via attacker-controlled node data.GHSA-j759-j44w-7fr8GHSA-x6wf-f3px-wcqxGHSA-f6ww-3ggp-fr8h
- Comment: throws when
datacontains-->- ProcessingInstruction: throws when
datacontains?>- DocumentType: throws when
publicIdfailsPubidLiteral,systemIdfailsSystemLiteral, orinternalSubsetcontains]>- Security: DOM traversal operations (
XMLSerializer.serializeToString(),Node.prototype.normalize(),Node.prototype.cloneNode(true),Document.prototype.importNode(node, true),node.textContentgetter,getElementsByTagName()/getElementsByTagNameNS()/getElementsByClassName()/getElementById()) are now iterative. Previously, deeply nested DOM trees would exhaust the JavaScript call stack and throw an unrecoverableRangeError.GHSA-2v35-w6hq-6mfwThank you,
@Jvr2022,@praveen-kv,@TharVid,@decsecre583,@tlsbollei,@KarimTantawey, for your contributionsCommits
bf396a50.9.1078f6089test: add missing serializer coverage for nodeFilter string return, Attribute...192ce5bci: remove unused imports flagged by CodeQLca81c06test: lower stack size for testsc9d5937style: npm run format1537fb4docs: add 0.9.10 changelog entryafd6f6fdocs: add 0.8.13 changelog entryafeb4eerefactor: align error mesage between branches4845ef1fix: prevent stack overflow in isEqualNode (GHSA-2v35-w6hq-6mfw)dfb94a4test: add missing isEqualNode behavioral coverage- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by karfau, a new releaser for
@xmldom/xmldomsince your current version.
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 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.Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802032778号
AWS Cloud Development Kit (AWS CDK) Toolkit
The AWS Cloud Development Kit (AWS CDK) is an open-source software development framework to define cloud infrastructure in code and provision it through AWS CloudFormation.
The AWS CDK consists of two main components:
This repository contains the code for the toolkit components. The class library repository is the main repository for the CDK project.
Getting Help
The best way to interact with our team is through GitHub, on the aws-cdk repository. You can open an issue and choose from one of our templates for bug reports, feature requests, documentation issues, or guidance.
If you have a support plan with AWS Support, you can also create a new support case.
You may also find help on these community resources:
aws-cdkContributing
We welcome community contributions and pull requests. See CONTRIBUTING.md for information on how to set up a development environment and submit code.
Structure of this repository
Here are the packages in this repository. See the README of each package for more information about it:
aws-cdkso you can runnpx cdkeven if it’s not installed.Every package comes with its own unit tests. There is a companion repository to this one containing the integration tests. You can find it here: https://github.com/aws/aws-cdk-cli-testing
See the contributing guide for more information on this repository.
Compatibility
The CLI is always able to process CDK apps using a version of the Construct Library released before it. We recommend you always keep the CLI version up-to-date to get the latest features.
For more details on the compatibility model and specific versions that work together, see COMPATIBILITY.md.