CVE-2012-2963
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 administrative interface in the embedded web server on the BreakingPoint Storm appliance before 3.0 does not require authentication for the gwt/BugReport script, which allows remote attackers to obtain sensitive information by downloading a .tgz file.
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 embedded web server in BreakingPoint Storm appliance versions before 3.0 lacks authentication enforcement on the gwt/BugReport script. This allows unauthenticated remote attackers to download a .tgz archive containing potentially sensitive system information through the administrative interface.
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 data<= 2.0= 1.2= 1.4= 1.5all 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.
-
Confirm you are running a BreakingPoint Storm ApplianceIdentify the device model and system information through the administrative interface or system console. Look for 'BreakingPoint Storm' or 'Breakingpointsystems' in the device identification.Affected if The device is a BreakingPoint Storm Appliance and the version is below 3.0, or for the Ctm variant, versions 1.2, 1.4, 1.5, or <=2.0
-
Check the firmware versionAccess the administrative web interface and navigate to the system information or firmware version page. Alternatively, use the console or CLI to retrieve the firmware version command output.Affected if The installed firmware version is below 3.0 (or for Ctm variant: 1.2, 1.4, 1.5, or <=2.0)
-
Verify the embedded web server is enabledCheck if the web-based administrative interface is running and accessible on the network. Confirm the HTTP/HTTPS service for the administrative interface is active.Affected if The web server is enabled and reachable on the network
-
Test unauthenticated access to BugReport endpointAttempt to access the URL path /gwt/BugReport through the web browser or curl command without providing any authentication credentials. For example: http://<device-ip>/gwt/BugReportAffected if The endpoint returns a .tgz archive or system information without requiring login credentials
You are affected if you have a BreakingPoint Storm Appliance with firmware version below 3.0 (or Ctm variant <=2.0/1.2/1.4/1.5), the web interface is enabled, and the /gwt/BugReport endpoint is accessible without authentication.
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 dataUpgrade the BreakingPoint Storm appliance to version 3.0 or later to obtain the patched firmware. As a compensating control, implement network-level access restrictions to limit who can reach the administrative web interface.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2963 — 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-2012-2963 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