CVE-2025-29786

一、漏洞信息
 漏洞编号：[CVE-2025-29786](https://nvd.nist.gov/vuln/detail/CVE-2025-29786)
 漏洞归属组件：[coredns](https://gitee.com/src-openeuler/coredns)
 漏洞归属的版本：1.11.3,1.7.0
 CVSS V3.0分值：
  BaseScore：7.5 High
  Vector：CVSS：3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr expression parser is given an unbounded input string, it will attempt to compile the entire string and generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size isn’t limited, a malicious or inadvertent extremely large expression can consume excessive memory as the parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM) crash of the process. This issue is relatively uncommon and will only manifest when there are no restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In typical use cases where inputs are bounded or validated, this problem would not occur. The problem has been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the number of AST nodes and memory usage during parsing, preventing any single expression from exhausting resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In practice, this means validating or limiting the length of expression strings that your application will accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.
 漏洞公开时间：2025-03-17 22:15:22
 漏洞创建时间：2025-05-29 11:39:06
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-29786
<details>
<summary>更多参考(点击展开)</summary>

无
</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  七彩瞬析开源风险感知平台
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| expr-lang/expr |  | https://github.com/expr-lang/expr/commit/0d19441454426d2f58edb22c31f3ba5f99c7a26e.patch |  | ljqc |

</details>
 
二、漏洞分析结构反馈
 影响性分析说明：
  
 openEuler评分：
   
 受影响版本排查(受影响/不受影响)：
  1.master(1.11.3):
2.openEuler-20.03-LTS-SP4(1.7.0):
3.openEuler-22.03-LTS-SP3(1.7.0):
4.openEuler-22.03-LTS-SP4(1.7.0):
5.openEuler-24.03-LTS(1.7.0):
6.openEuler-24.03-LTS-Next(1.7.0):
7.openEuler-24.03-LTS-SP1(1.7.0):
8.openEuler-24.03-LTS-SP2(1.7.0):

修复是否涉及abi变化(是/否)：
  1.master(1.11.3):
2.openEuler-20.03-LTS-SP4(1.7.0):
3.openEuler-22.03-LTS-SP3(1.7.0):
4.openEuler-22.03-LTS-SP4(1.7.0):
5.openEuler-24.03-LTS(1.7.0):
6.openEuler-24.03-LTS-Next(1.7.0):
7.openEuler-24.03-LTS-SP1(1.7.0):
8.openEuler-24.03-LTS-SP2(1.7.0):

原因说明：
  1.master(1.11.3):
2.openEuler-20.03-LTS-SP4(1.7.0):
3.openEuler-22.03-LTS-SP3(1.7.0):
4.openEuler-22.03-LTS-SP4(1.7.0):
5.openEuler-24.03-LTS(1.7.0):
6.openEuler-24.03-LTS-Next(1.7.0):
7.openEuler-24.03-LTS-SP1(1.7.0):
8.openEuler-24.03-LTS-SP2(1.7.0):

src-openEuler/coredns

Content Risk Flag

Comments (4)

src-openEuler/coredns .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2025-29786

Comments (4)

Search

src-openEuler/coredns