symfony: Composer audit fails for symfony/security-http 6.4.15 (newest version)

Symfony version(s) affected

6.4.15

Description

When running composer audit it fails:

composer audit
Found 1 security vulnerability advisory affecting 1 package:
+-------------------+----------------------------------------------------------------------------------+
| Package           | symfony/security-http                                                            |
| Severity          | medium                                                                           |
| CVE               | CVE-2024-36611                                                                   |
| Title             | Symfony http-security has authentication bypass                                  |
| URL               | https://github.com/advisories/GHSA-7q22-x757-cmgc                                |
| Affected versions | <7.1.0                                                                           |
| Reported at       | 2024-11-29T21:31:03+00:00                                                        |
+-------------------+----------------------------------------------------------------------------------+
composer info | grep symfony/security-http
symfony/security-http   6.4.15     Symfony Security Component - HTTP Integration

How to reproduce

Run composer audit having symfony/security-http@6.4.15 installed.

Possible Solution

Cherry-pick https://github.com/symfony/symfony/pull/53851 to 6.x.

Additional Context

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 19
  • Comments: 22 (20 by maintainers)

Commits related to this issue

Most upvoted comments

We’ve just updated the DB to ignore those in packagist.org so composer audit is green again.

CVE ignored by Packagist (composer audit) Advisory ignored by roave/security-advisories Advisory withdrawn by GitHub Revocation of CVE by mitre.org in progress

We can close this issue.

Those CVE have not been declared by the Symfony team. Apparently, someone reported CVEs for things that were considered regular bugfixes.

This, as well as CVE-2024-36610 (https://github.com/advisories/GHSA-cg28-v4wq-whv5) also need back-porting to Symfony 5.4.

Either they are security issues and should be backported to 6.x and 5.x, or they are not security issues. In which case the advistories should be withdrawn, as well as the roave/security-advisories entries.

See also Daniel Stenberg’s take on these bogus reports.

@derrabus indeed, we cannot. We would have to manage to convince MITRE to reject those CVEs. And this is not easy. For instance, curl went as far as becoming a CNA themselves to be able to avoid bogus CVEs (by being the sole CNA allowed to issue CVEs for curl). See some of the articles in the security category of badger’s blog if you don’t know that story yet.

Any hints about how/who created these bogus entries? Something is very wrong here, that’s a supply chain attack vector.

@bobvandevijver Yes, but if I configure that locally, it won’t help anyone but myself.

Can we instead convince Composer to ignore those bogus CVEs? Might we easier after all.

cc @naderman @Seldaek

It would be nice to have a blog post about this that would inform a bit more widely, because at first I didn’t understand why if there is CVE, it doesn’t apply to the 5.x branch. I had a hard time putting together that it was created by bypassing the security team.

@jeckel see Roave/SecurityAdvisoriesBuilder#756

@nicolas-grekas you should read the post by the curl maintainer @fritzmg linked above: https://daniel.haxx.se/blog/2024/02/21/disputed-not-rejected/ - it’s indeed a problem of the CVE system.

@derrabus You can configure an ignore locally:

        "audit": {
            "abandoned": "report",
            "ignore": {
                "GHSA-7q22-x757-cmgc": "Bogus",
                "GHSA-cg28-v4wq-whv5": "Bogus"
            }
        }

the advistories should be withdrawn

We cannot withdraw what we haven’t issued, can we?