Scout false positive on Spring Core 7.x.x for CVE-2011-2730, CVE-2010-1622

Open
#226 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, spring
Domain
cli, security

Research direction

Start by reproducing the Docker Scout finding for spring-core@7.0.6 and compare its matching logic with the affected ranges stated for CVE-2011-2730 and CVE-2010-1622. Trace the dependency and advisory matching entry points; done means these CVEs are no longer reported against Spring Core 7.0.6 while genuinely affected versions remain detectable.

Written by the indexing model from the issue text.

Description

It seems this morning that Docker Scout has been flagging CVE-2011-2730 & CVE-2010-1622 against Spring Core 7, specifically 7.0.6

This would appear to be a false positive.

CVE-2011-2730

Spring EL/JSP tag vulnerability in very old Spring 2.5/3.0 lines. Scout attached it to spring-core@7.0.6, but the advisory's affected range is <= 2.5.7.SR022, and the issue is about Spring JSP taglibs, not modern spring-core.

CVE-2010-1622

Spring data-binding RCE in Spring 2.5.x / 3.0.x before fixed releases. Scout again attached it to spring-core@7.0.6 even though the reported affected range is <= 2.5.6.SEC01 / 3.0.3.RELEASE.

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

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.

More from docker/scout-cli

All issues in docker/scout-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.