docker / docker/scout-cli

Markdown table syntax regression in Sarif report

Open
#217 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
454
Forks
134
PR merge metrics
No merged PRs in 30d

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/logback-core@1.5.32                                     |
| 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/logback-core@1.5.32  |
|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]]                                                |

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
docker, shell
Domain
cli, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.