CVE-1999-0517

highpriority · attend · 50EPSS 0.287 · 98 %ileexploit · functionalDEEUUS
grimoire priorityP1 · Urgent
Exploitable?
Public exploit
3 exploits · functional
Likely / severe?
28.7% (98th) EPSS
CVSS 7.5 · high
Is it mine?
84 products
Check your exposure
Who says so?
2 sources
enisa_euvd · murrelektronik_psirt

EPSS · scored 2026-10-22

An SNMP community name is the default (e.g. public), null, or missing.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

No fix is available; mitigate or reduce exposure.

  • No fix availablemurrelektronik_psirt

    A firmware update addressing the vulnerability is planned for early 2027 for the Impact67 Pro (article numbers 54620, 54630) and MVK Pro (article numbers 54600, 54610) product variants.

  • No fix plannedmurrelektronik_psirt

    No fixed planned

02

cvss

Technical severity, 0–10. One row per scoring source.

7.5
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.8–7.5

v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Pprimary · NVD / NIST USexploitability 10 · impact 6.4
v2.07.5highAV:N/AC:L/Au:N/C:P/I:P/A:Psecondary · Murrelektronik PSIRT
v3.15.9mediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lsecondary · ENISA EU
v3.15.9mediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:Lsecondaryexploitability 2.5 · impact 3.4
v3.15.8mediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:Fsecondary · CVSS-BT (t0sche)
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

05

exploits (3)

Public proof-of-concept and weaponised exploit code.

06

affected products (84)

Products and version ranges known to be affected.

showing 20 of 84
07

advisories (1)

Vendor and ecosystem advisories describing this.

  • VDE-2026-062Several Murrelektronik Devices use Default SNMP Community Names2026-07-14csaf · murrelektronik_psirtDE

    Several Murrelektronik devices using Profinet are shipped with the default SNMP community names ('public' for read access and 'private' for write access). If these community strings remain unchanged in the field, an unauthenticated attacker with network access to the device can read its configuration and, depending on the writable OIDs, modify device settings.

08

also known as (2)

Other names and identifiers for this entity.

09

sources

Which sources assert this record, and when.

published 1997-01-01modified 2026-06-16
10

references (4)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan