Skip to content

Update dependency pycares to v4.9.0 [SECURITY]#62

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/pypi-pycares-vulnerability
Open

Update dependency pycares to v4.9.0 [SECURITY]#62
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/pypi-pycares-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jun 16, 2025

This PR contains the following updates:

Package Change Age Confidence
pycares ==4.4.0==4.9.0 age confidence

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in pycares

GHSA-c58j-88f5-h53f

More information

Details

Impact

pycares versions < 4.2.0 are affected by CVE-2021-3672.

Patches

Update to version 4.2.0.

Severity

  • CVSS Score: 5.6 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


pycares has a Use-After-Free Vulnerability

GHSA-5qpg-rh4j-qp35

More information

Details

Summary

pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending. This results in a fatal Python error and interpreter crash.

Details
Root Cause

The vulnerability stems from improper handling of callback references when the Channel object is destroyed:

  1. When a DNS query is initiated, pycares stores a callback reference using ffi.new_handle()
  2. If the Channel object is garbage collected while queries are pending, the callback references become invalid
  3. When c-ares attempts to invoke the callback, it accesses freed memory, causing a fatal error

This issue was much more likely to occur when using event_thread=True but could happen without it under the right circumstances.

Technical Details

The core issue is a race condition between Python's garbage collector and c-ares's callback execution:

  1. When __del__ is called from within a c-ares callback context, we cannot immediately call ares_destroy() because c-ares is still executing code after the callback returns
  2. c-ares needs to execute cleanup code after our Python callback returns (specifically at lines 1422-1429 in ares_process.c)
  3. If we destroy the channel too quickly, c-ares accesses freed memory
Impact

Applications using pycares can be crashed remotely by triggering DNS queries that result in Channel objects being garbage collected before query completion. This is particularly problematic in scenarios where:

  • Channel objects are created per-request
  • Multiple failed DNS queries are processed rapidly
  • The application doesn't properly manage Channel lifecycle

The error manifests as:

Fatal Python error: b_from_handle: ffi.from_handle() detected that the address passed points to garbage
Fix

The vulnerability has been fixed in pycares 4.9.0 by implementing a safe channel destruction mechanism

Mitigation
For Application Developers
  1. Upgrade to pycares >= 4.9.0 - This version includes the fix and requires no code changes
  2. Best practices (optional but recommended):
    # Explicit cleanup
    channel.close()
    
    # Or use context manager
    with pycares.Channel() as channel:
        # ... use channel ...
    # Automatically closed
  3. Avoid creating Channel objects per-request - Prefer long-lived instances for better performance and safety

The fix is completely transparent - no API changes or code modifications are required.

Credit

This vulnerability was reported by @​vEpiphyte through the aio-libs security program.

Severity

Medium

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

saghul/pycares (pycares)

v4.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: saghul/pycares@v4.8.0...v4.9.0

v4.8.0

Compare Source

What's Changed

Full Changelog: saghul/pycares@v4.7.0...v4.8.0

v4.7.0: 4.7.0

Compare Source

What's Changed

Full Changelog: saghul/pycares@v4.6.1...v4.7.0

v4.6.1: 4.6.1

Compare Source

What's Changed

Full Changelog: saghul/pycares@v4.6.0...v4.6.1

v4.6.0: 4.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: saghul/pycares@v4.5.0...v4.6.0

v4.5.0: 4.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: saghul/pycares@v4.4.0...v4.5.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot changed the title Update dependency pycares to v4.9.0 [SECURITY] Update dependency pycares to v4.9.0 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/pypi-pycares-vulnerability branch March 27, 2026 00:44
@renovate renovate Bot changed the title Update dependency pycares to v4.9.0 [SECURITY] - autoclosed Update dependency pycares to v4.9.0 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/pypi-pycares-vulnerability branch 2 times, most recently from 19b1c16 to a4eb74b Compare March 30, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants