Create cve-2022-35829.yaml

[github-actions[bot]]

@check-spelling-bot Report

:red_circle: Please review

See the :open_file_folder: files view or the :scroll:action log for details.

Unrecognized words (12)

``` blog cloudapp CSTI Deployer fabrixss korniko Lidor msrc Sagi SFX SFXv Shitrit ```

To accept :heavy_check_mark: these unrecognized words as correct, run the following commands

... in a clone of the [git@github.com:wiz-sec/open-cvdb.git](https://github.com/wiz-sec/open-cvdb.git) repository on the `korniko98-patch-1` branch ([:information_source: how do I use this?]( https://github.com/check-spelling/check-spelling/wiki/Accepting-Suggestions)): ``` sh update_files() { perl -e ' my $new_expect_file=".github/actions/spelling/expect.txt"; use File::Path qw(make_path); use File::Basename qw(dirname); make_path (dirname($new_expect_file)); open FILE, q{<}, $new_expect_file; chomp(my @words = ); close FILE; my @add=qw('"$patch_add"'); my %items; @items{@words} = @words x (1); @items{@add} = @add x (1); @words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items; open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; }; close FILE; system("git", "add", $new_expect_file); ' } comment_json=$(mktemp) curl -L -s -S \ -H "Content-Type: application/json" \ "https://api.github.com/repos/wiz-sec/open-cvdb/issues/comments/1285155908" > "$comment_json" comment_body=$(mktemp) jq -r ".body // empty" "$comment_json" | tr -d "\\r" > $comment_body rm $comment_json patch_add=$(perl -e '$/=undef; $_=<>; if (m{Unrecognized words[^<]*\n*```\n*([^<]*)```\n*

$}m) { print "$1" } elsif (m{Unrecognized words[^<]*\n\n((?:\w.*\n)+)\n}m) { print "$1" };' < "$comment_body") update_files rm $comment_body git add -u ```

To have the bot do this for you, reply quoting the following line: @check-spelling-bot apply changes.

If the flagged items are false positives

If items relate to a ... * binary file (or some other file you wouldn't want to check at all). Please add a file path to the `excludes.txt` file matching the containing file. File paths are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files. `^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md]( ../tree/HEAD/README.md) (on whichever branch you're using). * well-formed pattern. If you can write a [pattern](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns) that would match it, try adding it to the `patterns.txt` file. Patterns are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines. Note that patterns can't match multiline strings.

[github-actions[bot]]

@check-spelling-bot Report

:red_circle: Please review

See the :open_file_folder: files view or the :scroll:action log for details.

Unrecognized words (12)

``` blog cloudapp CSTI Deployer fabrixss korniko Lidor msrc Sagi SFX SFXv Shitrit ```

To accept :heavy_check_mark: these unrecognized words as correct, run the following commands

... in a clone of the [git@github.com:wiz-sec/open-cvdb.git](https://github.com/wiz-sec/open-cvdb.git) repository on the `korniko98-patch-1` branch ([:information_source: how do I use this?]( https://github.com/check-spelling/check-spelling/wiki/Accepting-Suggestions)): ``` sh update_files() { perl -e ' my $new_expect_file=".github/actions/spelling/expect.txt"; use File::Path qw(make_path); use File::Basename qw(dirname); make_path (dirname($new_expect_file)); open FILE, q{<}, $new_expect_file; chomp(my @words = ); close FILE; my @add=qw('"$patch_add"'); my %items; @items{@words} = @words x (1); @items{@add} = @add x (1); @words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items; open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; }; close FILE; system("git", "add", $new_expect_file); ' } comment_json=$(mktemp) curl -L -s -S \ -H "Content-Type: application/json" \ "https://api.github.com/repos/wiz-sec/open-cvdb/issues/comments/1285171593" > "$comment_json" comment_body=$(mktemp) jq -r ".body // empty" "$comment_json" | tr -d "\\r" > $comment_body rm $comment_json patch_add=$(perl -e '$/=undef; $_=<>; if (m{Unrecognized words[^<]*\n*```\n*([^<]*)```\n*

$}m) { print "$1" } elsif (m{Unrecognized words[^<]*\n\n((?:\w.*\n)+)\n}m) { print "$1" };' < "$comment_body") update_files rm $comment_body git add -u ```

To have the bot do this for you, reply quoting the following line: @check-spelling-bot apply changes.

If the flagged items are false positives

If items relate to a ... * binary file (or some other file you wouldn't want to check at all). Please add a file path to the `excludes.txt` file matching the containing file. File paths are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files. `^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md]( ../tree/HEAD/README.md) (on whichever branch you're using). * well-formed pattern. If you can write a [pattern](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns) that would match it, try adding it to the `patterns.txt` file. Patterns are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines. Note that patterns can't match multiline strings.

[github-actions[bot]]

@check-spelling-bot Report

:red_circle: Please review

See the :open_file_folder: files view or the :scroll:action log for details.

Unrecognized words (4)

korniko Lidor Sagi Shitrit

To accept :heavy_check_mark: these unrecognized words as correct, run the following commands

... in a clone of the [git@github.com:wiz-sec/open-cvdb.git](https://github.com/wiz-sec/open-cvdb.git) repository on the `korniko98-patch-1` branch ([:information_source: how do I use this?]( https://github.com/check-spelling/check-spelling/wiki/Accepting-Suggestions)): ``` sh update_files() { perl -e ' my $new_expect_file=".github/actions/spelling/expect.txt"; use File::Path qw(make_path); use File::Basename qw(dirname); make_path (dirname($new_expect_file)); open FILE, q{<}, $new_expect_file; chomp(my @words = ); close FILE; my @add=qw('"$patch_add"'); my %items; @items{@words} = @words x (1); @items{@add} = @add x (1); @words = sort {lc($a)."-".$a cmp lc($b)."-".$b} keys %items; open FILE, q{>}, $new_expect_file; for my $word (@words) { print FILE "$word\n" if $word =~ /\w/; }; close FILE; system("git", "add", $new_expect_file); ' } comment_json=$(mktemp) curl -L -s -S \ -H "Content-Type: application/json" \ "https://api.github.com/repos/wiz-sec/open-cvdb/issues/comments/1285174917" > "$comment_json" comment_body=$(mktemp) jq -r ".body // empty" "$comment_json" | tr -d "\\r" > $comment_body rm $comment_json patch_add=$(perl -e '$/=undef; $_=<>; if (m{Unrecognized words[^<]*\n*```\n*([^<]*)```\n*

$}m) { print "$1" } elsif (m{Unrecognized words[^<]*\n\n((?:\w.*\n)+)\n}m) { print "$1" };' < "$comment_body") update_files rm $comment_body git add -u ```

To have the bot do this for you, reply quoting the following line: @check-spelling-bot apply changes.

If the flagged items are false positives

If items relate to a ... * binary file (or some other file you wouldn't want to check at all). Please add a file path to the `excludes.txt` file matching the containing file. File paths are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files. `^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md]( ../tree/HEAD/README.md) (on whichever branch you're using). * well-formed pattern. If you can write a [pattern](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns) that would match it, try adding it to the `patterns.txt` file. Patterns are Perl 5 Regular Expressions - you can [test]( https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines. Note that patterns can't match multiline strings.