Bug 2553106 - CVE-2026-109438 3proxy: 3proxy: Information disclosure via uninitialized stack memory in SOCKS reply [epel-all]
Summary: CVE-2026-109438 3proxy: 3proxy: Information disclosure via uninitialized stac...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: 3proxy
Version: epel10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Tim Semeijn
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["ee3cb8e3-aa6f-4ca9-8128-9...
Depends On:
Blocks: CVE-2026-109438
TreeView+ depends on / blocked
 
Reported: 2026-10-15 08:47 UTC by Vladimir Vasilev
Modified: 2026-10-22 23:01 UTC (History)
3 users (show)

Fixed In Version: 3proxy-1.0.1-2.fc46
Clone Of:
Environment:
Last Closed: 2026-10-22 23:01:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Vasilev 2026-10-15 08:47:40 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

3proxy from 0.9.7 through 1.0.1, fixed in commit 206c923, contains an uninitialized stack memory disclosure vulnerability that allows unauthenticated attackers to leak stack bytes via the SOCKS4 reply path when the external-NAT option (-Ne) is configured. Attackers can send a client probe that fails the SOCKS version check to trigger a reply containing uninitialized bytes from the sin structure, exposing high bytes of a userspace pointer that weakens ASLR protections.

Comment 1 Fedora Update System 2026-10-22 22:56:18 UTC
FEDORA-2026-0d57adddb7 (3proxy-1.0.1-2.fc46) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-0d57adddb7

Comment 2 Fedora Update System 2026-10-22 23:01:11 UTC
FEDORA-2026-0d57adddb7 (3proxy-1.0.1-2.fc46) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.