CVE-2024-34149

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check for example, because they agree with the objective but disagree with the technical mechanism, ...

CVE-2024-34149

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check for example, because they agree with the objective but disagree with the technical mechanism, ...

CVE-2024-34149

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check for example, because they agree with the objective but disagree with the technical mechanism, ...

CVE-2024-34149

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check for example, because they agree with the objective but disagree with the technical mechanism, ...

CVE-2024-34149

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check for example, because they agree with the objective but disagree with the technical mechanism, ...

PT-2024-25720

Name of the Vulnerable Software and Affected Versions Bitcoin Core versions through 27.0 Bitcoin Knots versions prior to 25.1.knots20231115 Description The tapscript implementation does not include a policy size limit check. This is a separate issue from CVE-2023-50428. Some parties have expresse...

CVE-2024-34149

CVE-2024-34149 affects Bitcoin Core up to version 27.0 and Bitcoin Knots up to 25.1.knots20231115, where tapscript lacks a policy size limit check. Root cause: missing policy size limit in tapscript. The connected Red Hat/CVE entries confirm the same description with no additional exploit details...