CVE-2024-41798
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been identified in SENTRON 7KM PAC3200 (All versions). Affected devices only provide a 4-digit PIN to protect from administrative access via Modbus TCP interface. Attackers with access to the Modbus TCP interface could easily bypass this protection by brute-force attacks or by sniffing the Modbus clear text communication.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe SENTRON 7KM PAC3200 power measurement device uses a weak 4-digit PIN (only 10,000 possible combinations) to protect administrative access via Modbus TCP. This PIN is vulnerable to trivial brute-force attacks, and because Modbus communication is transmitted in clear text, the PIN can also be captured by network sniffing, allowing attackers to gain full administrative access to the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLocate the SENTRON 7KM PAC3200 power measurement device in your asset inventory or physically on the network. Confirm the exact model number matches '7KM PAC3200'.Affected if The device model is SENTRON 7KM PAC3200 and the device is in use.
-
Confirm Modbus TCP is enabledAccess the device web interface or documentation to verify whether the Modbus TCP interface is enabled and actively listening on port 502. Check device configuration for 'Modbus TCP' or 'Modbus TCP/IP' settings.Affected if Modbus TCP is enabled and configured on the device.
-
Check PIN configurationAccess the device administrative interface and navigate to security or authentication settings. Verify the administrative PIN length and complexity. The device uses a 4-digit PIN (10,000 possible combinations).Affected if A 4-digit numeric PIN is configured for administrative access via Modbus TCP.
-
Assess network exposureScan the network to determine if the Modbus TCP port (502/tcp) is accessible from network segments outside your trusted control plane or from untrusted endpoints. Use tools like 'nmap -p 502 <target>' to test accessibility.Affected if Port 502/TCP is reachable from untrusted networks or unauthorized IP addresses.
Your environment is affected if you have a SENTRON 7KM PAC3200 device with Modbus TCP enabled and a 4-digit PIN configured, especially if the Modbus interface is accessible from less trusted network segments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate affected devices on a dedicated network segment with strict access controls, implement firewall rules limiting Modbus TCP access to authorized endpoints only, and consider replacing the device with a newer model supporting stronger authentication mechanisms such as certificate-based authentication.
- Consultation12.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41798 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-41798 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data