GHSA-P5WF-CMR4-XRWR

Permissive Regular Expression in tacquito

Workarounds

Users should be able to add boundary conditions anchors '^' and '$' to their command configs to remediate the vulnerability without the upgrade

The CVE is for a software vulnerability. Network admins who have deployed tacquito (or versions of tacquito) in their production environments and use tacquito to perform command authorization for network devices should be impacted.

Tacquito code prior to commit 07b49d1358e6ec0b5aa482fcd284f509191119e2 was performing regex matches on authorized commands and arguments in a more permissive than intended manner. Configured allowed commands/arguments were intended to require a match on the entire string, but instead only enforced a match on a sub-string. This behaviour could potentially allowed unauthorized commands to be executed.

A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use. Typical impact: denial of service when input is crafted to trigger backtracking.

GHSA-P5WF-CMR4-XRWR has a CVSS score of 7.6 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20241011192817-07b49d1358e6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been patched, and users should update to the latest github repo commit to get the patch.

1. What is GHSA-P5WF-CMR4-XRWR? GHSA-P5WF-CMR4-XRWR is a high-severity inefficient regular expression (ReDoS) vulnerability in github.com/facebookincubator/tacquito (go), affecting versions < 0.0.0-20241011192817-07b49d1358e6. It is fixed in 0.0.0-20241011192817-07b49d1358e6. A regular expression with worst-case exponential or polynomial matching time is applied to untrusted input, causing excessive CPU use.
2. How severe is GHSA-P5WF-CMR4-XRWR? GHSA-P5WF-CMR4-XRWR has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/facebookincubator/tacquito are affected by GHSA-P5WF-CMR4-XRWR? github.com/facebookincubator/tacquito (go) versions < 0.0.0-20241011192817-07b49d1358e6 is affected.
4. Is there a fix for GHSA-P5WF-CMR4-XRWR? Yes. GHSA-P5WF-CMR4-XRWR is fixed in 0.0.0-20241011192817-07b49d1358e6. Upgrade to this version or later.
5. Is GHSA-P5WF-CMR4-XRWR exploitable, and should I be worried? Whether GHSA-P5WF-CMR4-XRWR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-P5WF-CMR4-XRWR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-P5WF-CMR4-XRWR? Upgrade github.com/facebookincubator/tacquito to 0.0.0-20241011192817-07b49d1358e6 or later.