CVE-2009-0474
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 · uneditedThe web interface in the Rockwell Automation ControlLogix 1756-ENBT/A EtherNet/IP Bridge Module allows remote attackers to obtain "internal web page information" and "internal information about the module" via unspecified vectors. NOTE: this may overlap CVE-2002-1603.
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 · moderate confidenceThe web interface of the Rockwell Automation ControlLogix 1756-ENBT/A EtherNet/IP Bridge Module contains an information disclosure vulnerability allowing remote attackers to obtain internal web page content and module information via unspecified vectors. This is a confidentiality-focused flaw in an industrial control system device's embedded web server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 the 1756-ENBT/A module on the networkScan the network for devices responding to EtherNet/IP (port 44818) or HTTP (port 80) with a web interface showing Rockwell Automation or Controllogix branding. Check network scans for MAC OUI 00-1D-9C (Rockwell) or device type identifiers.Affected if The 1756-ENBT/A EtherNet/IP Bridge Module is present and network-accessible.
-
Verify the web interface is enabledAttempt HTTP access to the device IP address on port 80 (or configured web port). Confirm the web server responds and displays Controllogix or 1756-ENBT related content.Affected if The embedded web server is active and responds to HTTP requests.
-
Check for unauthenticated information disclosureAccess common web paths such as /, /index.html, or /home.htm. Observe whether the page returns module configuration details, firmware version, IP settings, or other internal information without requiring authentication.Affected if Internal web page content and module information are returned without authentication.
-
Assess network exposureReview firewall rules, ACLs, and network segmentation to determine if the device web interface is reachable from untrusted networks, the corporate network, or the internet.Affected if The device web interface is accessible from networks outside the trusted control system segment.
The environment is affected if a 1756-ENBT/A module with its web interface enabled is present and accessible from any network segment that includes untrusted or unauthorized hosts.
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 dataIf available, apply vendor-provided firmware updates for the 1756-ENBT module. Otherwise, isolate the device on a restricted network segment, disable the web interface if not operationally required, and implement firewall rules to limit access to trusted hosts only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0474 — 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-2009-0474 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