CVE-2016-2509 is a flaw in the password sync feature of Hirschmann Classic Platform switches: the switch passwords become the SNMPv1/v2 community strings, which cross the network in clear text, so anyone sniffing the local network can recover the administrator password. NVD scores it 5.3. Belden fixes it in Classic 09.0.06 and L2B 05.3.07, followed by disabling the sync and SNMPv1/v2.
Vulnerability summary
CVSS base score
5.3
Medium severity
EPSS score (FIRST)
0.8%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2016-2509 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Hirschmann Classic L2E, L2P, L3E and L3P switches: RS, RSR, MACH100, MACH1000, MACH4000, MS, OCTOPUS | cpe:2.3:o:belden:hirschmann_firmware:*:*:*:*:*:*:*:* | 09.0.05 and lower; fixed in 09.0.06 or higher (Belden BSECV-2016-2) |
| Hirschmann Classic L2B switches: RSB | cpe:2.3:o:belden:hirschmann_firmware:05.3.06:*:*:*:*:*:*:* | 05.3.06 and lower; fixed in 05.3.07 or higher (Belden BSECV-2016-2) |
What does this mean for affected devices?
NVD carries the CERT/CC description: "The password-sync feature on Belden Hirschmann Classic Platform switches L2B before 05.3.07 and L2E, L2P, L3E, and L3P before 09.0.06 sets an SNMP community to the same string as the administrator password, which allows remote attackers to obtain sensitive information by sniffing the network." NVD's Primary score is CVSS v3.0 5.3 (CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), v2 2.9, with CWE-200 (exposure of sensitive information). CERT/CC published the record on 2016-02-18 (NVD, CVE record).
What does the password sync feature do?
Belden bulletin BSECV-2016-2 explains that on all Hirschmann Classic Platform switches, by default, the switch "user" and "admin" passwords are used to build the matching SNMPv1/v2 read-only and read-write community strings. SNMPv1/v2 travels unencrypted, so an attacker on the local network who can sniff traffic may recover the passwords from the community strings when the switch is managed over SNMPv1/v2. The bulletin adds that the community strings are also stored in plain text in the configuration file. Belden's impact statement is direct: the attacker may learn both passwords "and thereby achieve full administration access to the switch" (Belden BSECV-2016-2).
CERT/CC note VU#507216 classes the same flaw as CWE-257 (storing passwords in a recoverable form) and records that Hirschmann enabled the feature by default to ease the move from SNMPv1/v2 to SNMPv3, and committed to turning it off by default in future devices and firmware (CERT/CC VU#507216). The NVD score stays at 5.3 because the attacker has to be on the adjacent network and has to catch SNMP traffic; the result of a successful capture is full control of the switch.
Which switches and firmware are affected?
BSECV-2016-2 (version 1.1, 2016-12-19) lists the Classic L2E, L2P, L3E and L3P platforms on RS, RSR, MACH100, MACH1000, MACH4000, MS and OCTOPUS at 09.0.05 and lower, and the Classic L2B platform on RSB at 05.3.06 and lower. The fixed releases are 09.0.06 or higher and 05.3.07 or higher. NVD's configuration matches the Hirschmann firmware up to 09.0.05 with the L2E, L2P, L3E and L3P platforms, and firmware 05.3.06 with L2B.
How do you fix and harden it?
Update first, then change the configuration, because Belden asks for the suggested actions after the update and reboot. On 09.0.00 and higher: disable the SNMP password synchronization (CLI no snmp sync v3-to-community and no snmp sync community-to-v3), set the SNMPv1/v2 communities back to the defaults, disable SNMPv1/v2 globally, change the read and read/write passwords and save the configuration. Below 09.0.00 there is no sync switch: change the passwords, reset the communities, disable SNMPv1/v2 and save, and repeat the community reset every time a password changes. CERT/CC also recommends SNMPv3, which encrypts the traffic.
Any password that ever travelled as an SNMPv1/v2 community on that network should be treated as known and rotated. The Hirschmann and Belden switch vulnerability guide puts this flaw next to the Classic web flaws such as CVE-2018-5469, and CVE-2002-0013 shows how old the SNMPv1 attack surface is. Our Net-SNMP and SNMP agent guide covers community handling on embedded agents.
CVE-2016-2509 is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.00796, the 57.4th percentile, in the 2026-11-20 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD (read 2026-11-21): status Modified; published 2016-02-18 by CERT/CC; NVD Primary CVSS v3.0 5.3 CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, v2 2.9; CWE-200; CPEs Hirschmann firmware up to 09.0.05 with L2E/L2P/L3E/L3P and firmware 05.3.06 with L2B; references VU#507216 and BSECV-2016-2. — NVD
- Belden BSECV-2016-2 version 1.1 (2016-12-19, first published 2016-02-16), read 2026-11-21: Classic L2E/L2P/L3E/L3P (RS, RSR, MACH100, MACH1000, MACH4000, MS, OCTOPUS) 09.0.05 and lower and Classic L2B (RSB) 05.3.06 and lower affected; fixed 09.0.06 or higher and 05.3.07 or higher; suggested actions disable password sync, reset communities to defaults, disable SNMPv1/v2, change passwords, save; below 09.0.00 the community reset must be repeated on every password change; community strings stored in plain text in the configuration file. — Belden BSECV-2016-2
- CERT/CC VU#507216, read 2026-11-21: CWE-257; administrator password recoverable from SNMP community string sent in plaintext in SNMPv1/v2; solution disable password sync and use SNMPv3; Hirschmann enabled the feature by default for the SNMPv1/v2 to SNMPv3 transition and committed to disabling it by default in future devices and firmware. — CERT/CC
- CVE record (checked 2026-11-21): state PUBLISHED, CNA CERT/CC (certcc), published 2016-02-18; no CNA CVSS metric. — CVE.org
- Not in the CISA KEV catalog, version 2026.11.20 (1,790 entries), checked 2026-11-21. — CISA KEV
- EPSS 0.00796, percentile 0.57381, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which firmware fixes CVE-2016-2509?
Belden BSECV-2016-2 names Classic 09.0.06 or higher for the L2E, L2P, L3E and L3P platforms (RS, RSR, MACH100, MACH1000, MACH4000, MS, OCTOPUS) and 05.3.07 or higher for the L2B platform (RSB). Belden asks for its configuration steps after the update and reboot.
What should I change on the switch?
On 09.0.00 and higher, disable the password synchronization (no snmp sync v3-to-community, no snmp sync community-to-v3), set the SNMPv1/v2 communities back to public and private, disable SNMPv1 and SNMPv2, change the passwords and save. Below 09.0.00, reset the communities after every password change.
Why is a flaw that reveals the admin password only 5.3?
NVD scores an adjacent-network attacker with high attack complexity and only a confidentiality impact. Belden's own impact statement is that the attacker may gain full administration access to the switch, so treat captured passwords as compromised.
Is CVE-2016-2509 exploited?
It is not in the CISA KEV catalog as of 2026-11-21 (version 2026.11.20). FIRST EPSS gives it 0.00796, the 57.4th percentile, in the 2026-11-20 dataset.
Questions about this page?