Markdown table syntax regression in Sarif report
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing docker scout cves --format sarif with a report containing the affected CVE, then inspect runs.tool.driver.rules.help.markdown in the generated SARIF. Compare the output with v1.18.4 and v1.19.0; done means the summary is emitted as a valid Markdown table again.
Written by the indexing model from the issue text.
Description
Hello 👋
The markdown syntax in the Sarif reports produced by docker scout cves --format sarif has broken since v1.19.0.
The summary table at the end of the CVE description (found in the report at runs.tool.driver.rules.help.markdown) is no longer a valid markdown table.
Example of table in report generated by v1.18.4:
| | |
|----------------|----------------------------------------------------------------------------------|
| Package | pkg:maven/ch.qos.logback/[email protected] |
| Affected range | <=1.5.32 |
| Fixed version | 1.5.33 |
| CVSS Score | 1.2 |
| CVSS Vector | CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:P/RE:L/U:Green |
The same table in report generated by v1.19.0 onwards:
| |
|Package pkg:maven/ch.qos.logback/[email protected] |
|Affected range <=1.5.32 |
|Fixed version 1.5.33 |
|[[CVSS Score 1.2] [CVSS Vector CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:P/RE:L/U:Green]] |
- Dominant language
- Shell
- Stars
- 455
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/scout-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
allstar
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
panic: nil deref in createVCS() scanning multi-arch image by tag when no attestation sidecar existsOpen
Difficulty 4/5 3-5 days Newbie friendliness 64/100
All issues in docker/scout-cli
Similar issues
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
catppuccin/kde#152 ·
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
msys2/MINGW-packages#32008 ·
Maintainers usually reply within 1 day
-
bot-found bug priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
madenvel/KalinkaPlayer#179 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100