GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GHSA-ww7x-3gxh-qm6rhigh7.5

Validation of SignedInfo

Check your stack

The advisory, in context

Validation of an XML Signature requires verification that the hash value of the related XML-document (after any optional transformations and/or normalizations) matches a specific DigestValue-value, but also that the cryptografic signature on the SignedInfo-tree (the one that contains the DigestValue) verifies and matches a trusted public key.

Within the simpleSAMLphp/xml-security library (https://github.com/simplesamlphp/xml-security), the hash is being validated using SignedElementTrait::validateReference, and the signature is being verified in SignedElementTrait::verifyInternal

https://github.com/simplesamlphp/xml-security/blob/master/src/XML/SignedElementTrait.php:

afbeelding

What stands out is that the signature is being calculated over the canonical version of the SignedInfo-tree. The validateReference method, however, uses the original non-canonicalized version of SignedInfo.

Impact

If an attacker somehow (i.e. by exploiting a bug in PHP's canonicalization function) manages to manipulate the canonicalized version's DigestValue, it would be potentially be possible to forge the signature. No possibilities to exploit this were found during the investigation.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

From 1.6.11 before 1.6.12

Fixed in 1.6.12

2 explicitly affected versions

1.6.11, v1.6.11

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "1.6.11"
        },
        {
          "fixed": "1.6.12"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.6.11",
    "v1.6.11"
  ]
}
Ecosystem versions

From 5.0.0-alpha.12 before 5.0.0-alpha.13

Fixed in 5.0.0-alpha.13

1 explicitly affected versions

5.0.0-alpha.12

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "5.0.0-alpha.12"
        },
        {
          "fixed": "5.0.0-alpha.13"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "5.0.0-alpha.12"
  ]
}

References