CVE-2025-31498

一、漏洞信息
 漏洞编号：[CVE-2025-31498](https://nvd.nist.gov/vuln/detail/CVE-2025-31498)
 漏洞归属组件：[c-ares](https://gitee.com/src-openeuler/c-ares)
 漏洞归属的版本：1.19.1,1.34.4,1.34.5
 CVSS V3.0分值：
  BaseScore：N/A None
  Vector：CVSS：3.0/
 漏洞简述：
  c-ares is an asynchronous resolver library. From 1.32.3 through 1.34.4, there is a use-after-free in read_answers() when process_answer() may re-enqueue a query either due to a DNS Cookie Failure or when the upstream server does not properly support EDNS, or possibly on TCP queries if the remote closed the connection immediately after a response. If there was an issue trying to put that new transaction on the wire, it would close the connection handle, but read_answers() was still expecting the connection handle to be available to possibly dequeue other responses. In theory a remote attacker might be able to trigger this by flooding the target with ICMP UNREACHABLE packets if they also control the upstream nameserver and can return a result with one of those conditions, this has been untested. Otherwise only a local attacker might be able to change system behavior to make send()/write() return a failure condition. This vulnerability is fixed in 1.34.5.
 漏洞公开时间：2025-04-08 22:15:35
 漏洞创建时间：2025-04-08 22:33:02
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2025-31498
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| security-advisories.github.com | https://github.com/c-ares/c-ares/commit/29d38719112639d8c0ba910254a3dd4f482ea2d1 |  |
| security-advisories.github.com | https://github.com/c-ares/c-ares/pull/821 |  |
| security-advisories.github.com | https://github.com/c-ares/c-ares/security/advisories/GHSA-6hxc-62jh-p29v |  |
| af854a3a-2127-422b-91ae-364da2661108 | http://www.openwall.com/lists/oss-security/2025/04/08/3 |  |
| suse_bugzilla | https://github.com/c-ares/c-ares/pull/821whereas | https://bugzilla.suse.com/show_bug.cgi?id=1240955 |
| suse_bugzilla | https://github.com/c-ares/c-ares/releases/tag/v1.34.5 | https://bugzilla.suse.com/show_bug.cgi?id=1240955 |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-31498 | https://bugzilla.suse.com/show_bug.cgi?id=1240955 |
| suse_bugzilla | https://seclists.org/oss-sec/2025/q2/27 | https://bugzilla.suse.com/show_bug.cgi?id=1240955 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2025:4459 | https://bugzilla.redhat.com/show_bug.cgi?id=2358271 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2025:4461 | https://bugzilla.redhat.com/show_bug.cgi?id=2358271 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2025:7426 | https://bugzilla.redhat.com/show_bug.cgi?id=2358271 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2025:7433 | https://bugzilla.redhat.com/show_bug.cgi?id=2358271 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2025:7502 | https://bugzilla.redhat.com/show_bug.cgi?id=2358271 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2025:7537 | https://bugzilla.redhat.com/show_bug.cgi?id=2358271 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2025-31498 |
| osv | https://github.com/c-ares/c-ares/security/advisories/GHSA-6hxc-62jh-p29v | https://osv.dev/vulnerability/CVE-2025-31498 |
| osv | https://github.com/c-ares/c-ares/commit/29d38719112639d8c0ba910254a3dd4f482ea2d1 | https://osv.dev/vulnerability/CVE-2025-31498 |
| osv | https://github.com/c-ares/c-ares/pull/821 | https://osv.dev/vulnerability/CVE-2025-31498 |
| osv | http://www.openwall.com/lists/oss-security/2025/04/08/3 | https://osv.dev/vulnerability/CVE-2025-31498 |
| osv | https://security.alpinelinux.org/vuln/CVE-2025-31498 | https://osv.dev/vulnerability/CVE-2025-31498 |
| osv | https://security-tracker.debian.org/tracker/CVE-2025-31498 | https://osv.dev/vulnerability/CVE-2025-31498 |
| amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2025-31498 | https://explore.alas.aws.amazon.com/CVE-2025-31498.html |
| amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31498 | https://explore.alas.aws.amazon.com/CVE-2025-31498.html |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://github.com/c-ares/c-ares/commit/29d38719112639d8c0ba910254a3dd4f482ea2d1 |  | security-advisories.github.com |
|  |  | https://github.com/c-ares/c-ares/pull/821 |  | security-advisories.github.com |
|  |  | https://github.com/c-ares/c-ares/pull/821whereas |  | suse_bugzilla |
|  |  | https://github.com/c-ares/c-ares/commit/29d38719112639d8c0ba910254a3dd4f482ea2d1 |  | osv |
|  |  | https://github.com/c-ares/c-ares/pull/821 |  | osv |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  From 1.32.3 through 1.34.4, there is a use-after-free in read_answers() when process_answer() may re-enqueue a query either due to a DNS Cookie Failure or when the upstream server does not properly support EDNS, or possibly on TCP queries if the remote closed the connection immediately after a response. If there was an issue trying to put that new transaction on the wire, it would close the connection handle, but read_answers() was still expecting the connection handle to be available to possibly dequeue other responses. In theory a remote attacker might be able to trigger this by flooding the target with ICMP UNREACHABLE packets if they also control the upstream nameserver and can return a result with one of those conditions, this has been untested. Otherwise only a local attacker might be able to change system behavior to make send()/write() return a failure condition.
 openEuler评分：
  6.5
 Vector：CVSS：3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
 受影响版本排查(受影响/不受影响)：
  1.master:受影响
2.openEuler-20.03-LTS-SP4:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.openEuler-24.03-LTS:不受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:不受影响
8.openEuler-24.03-LTS-SP2(1.19.1):不受影响

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

原因说明：
  1.master:正常修复
2.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP3:不受影响-漏洞代码不存在
4.openEuler-22.03-LTS-SP4:不受影响-漏洞代码不存在
5.openEuler-24.03-LTS:不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1:不受影响-漏洞代码不存在
8.openEuler-24.03-LTS-SP2(1.19.1):不受影响-漏洞代码不存在

src-openEuler/c-ares
Closed

Content Risk Flag

Comments (8)

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

Content Risk Flag

CVE-2025-31498

Comments (8)

Search

src-openEuler/c-ares
Closed