dbcve.org
Webspeed MessengerApplication · Progress

CVE-2007-2354

HIGH · 7.8 CVSS v2.0 Published 2007-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Progress Webspeed Messenger allows remote attackers to obtain sensitive information via a WService parameter containing "wsbroker1/webutil/about.r", which reveals the operating system and product information.

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 confidence

Progress Webspeed Messenger exposes sensitive OS and product version information through the webutil/about.r endpoint when accessed via the WService parameter, allowing remote attackers to gather reconnaissance data for further attacks.

MitigationDisable or restrict access to the wsbroker1/webutil/about.r endpoint via web server configuration or Webspeed broker settings to prevent unauthorized information disclosure.

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
Webspeed MessengerApplication
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Webspeed broker web interface is exposed
    Check if your Webspeed server responds on typical web broker ports (default: wsbroker1/webutil/)
    Affected if The wsbroker1/webutil/ endpoint is accessible without authentication
  2. Test for about.r endpoint accessibility
    Attempt to access http://[your-server]/wsbroker1/webutil/about.r or similar paths
    Affected if The about.r endpoint returns HTTP 200 and displays application content
  3. Check WService parameter behavior
    Try accessing the endpoint with WService parameter: /wsbroker1?WService=about.r
    Affected if The endpoint accepts WService parameter and returns information
  4. Verify information disclosure
    Examine the response from the about.r endpoint for OS version, product version, file paths, or configuration details
    Affected if The response contains sensitive OS details, Progress version numbers, or internal path information

If the wsbroker1/webutil/about.r endpoint is accessible and returns sensitive OS/product version information via the WService parameter, the environment is affected by CVE-2007-2355.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or restrict access to the wsbroker1/webutil/about.r endpoint via web server configuration or Webspeed broker settings to prevent unauthorized information disclosure.

Fix this in Webspeed Messenger Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2354 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2354 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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