ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
SMB
Application LayerProfessional trackAdvancedOSI: Application LayerDefault Port: 830Standard: RFC 6241

NETCONF

— Network Configuration Protocol

NETCONF replaces screen-scraping CLI automation with structured XML remote procedure calls. A manager opens an SSH subsystem on port 830, exchanges hello messages to learn capabilities, and then edits candidate or running datastores with transactions and rollback support.

Read first: SSH, TCPContent reviewed 2026-11-18

Interactive Session: How NETCONF Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of NETCONF.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

Unauthorised configuration change

Feature abuse

Reused SSH credentials or an over-privileged account allows a NETCONF client to change device configuration.

Attackersimulated
NETCONFtarget
Attack step 1 of 3
Log in over SSH

The attacker uses stolen or weak credentials on port 830.

What a defender can see

NETCONF sessions from new management hosts.

Impact if unmitigated

Network-wide misconfiguration or traffic redirection.

Defences that matter
  • SSH keys with MFA
  • NACM rules limiting each account
  • Configuration change approval and audit

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • XML-encoded RPC messages framed with end-of-message delimiters
  • Capability exchange in <hello> messages during session setup
  • Candidate datastore with <commit>, <discard-changes>, and rollback
  • Operations include <get-config>, <edit-config>, <copy-config>, <validate>

Real-World Use Cases

  • Automated configuration of routers and switches from an orchestrator
  • Transactional multi-device changes with rollback on failure
  • Model-driven telemetry and configuration with YANG modules

Advantages & Strengths

  • Structured, validated changes replace fragile CLI parsing
  • Commit and rollback make configuration changes atomic

Limitations & Vulnerabilities

  • XML payloads are verbose compared with JSON-based alternatives
  • Requires YANG models to describe device configuration correctly