Bug 2565448 - CVE-2026-63201 netopeer2: Netopeer2: Denial of Service via format string in get RPC filter [fedora-44]
Summary: CVE-2026-63201 netopeer2: Netopeer2: Denial of Service via format string in g...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: netopeer2
Version: 44
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Michal Ruprich
QA Contact:
URL:
Whiteboard: {"flaws": ["72ace307-2f95-460b-b132-2...
Depends On:
Blocks: CVE-2026-63201
TreeView+ depends on / blocked
 
Reported: 2026-11-03 02:04 UTC by Ganesh
Modified: 2026-11-03 02:04 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-11-03 02:04:26 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.

Netopeer2 is a server for implementing network configuration management based on the `NETCONF` Protocol. In affected versions, a low-privileged authenticated `NETCONF` user can remotely crash `netopeer2-server` by sending a `get RPC` with an invalid `subtree filter` whose text contains format specifiers. In `src/netconf.c`, `np2srv_rpc_get_cb()` sends the invalid value through `ERR()` to `np2log_printf()`, where `vsnprintf()` first formats the message safely. In `src/log.c`, that already formatted buffer is subsequently passed to `np2log()` as the format string itself, causing `vsyslog()` to interpret attacker-controlled percent sequences and read invalid pointer arguments. The reported denial of service was confirmed on version 2.8.7 using `NETCONF`-over-SSH and AddressSanitizer; reliable remote code execution was not confirmed. `The advisory identifies 2.8.8 as patched`; repository comparisons verify the fix in public release 2.8.21. The affected/fixed boundary remains unresolved because no public 2.8.8 tag was located, which does not establish the status of an untagged 2.8.8 build.


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