dbcve.org
Appeon For PowerbuilderApplication · Sybase

CVE-2011-0497

HIGH · 7.8 CVSS v2.0 Published 2011-01-20
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
Directory traversal vulnerability in Sybase EAServer 6.x before 6.3 ESD#2, as used in Appeon, Replication Server Messaging Edition (RSME), and WorkSpace, allows remote attackers to read arbitrary files via "../\" (dot dot forward-slash backslash) sequences in a crafted request.

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

Directory traversal vulnerability in Sybase EAServer 6.x before version 6.3 ESD#2 allows remote attackers to read arbitrary files on the server by using '../\' (dot-dot-forward-slash-backslash) sequences in crafted HTTP requests. The vulnerability affects Appeon, Replication Server Messaging Edition (RSME), and WorkSpace components.

MitigationApply Sybase EAServer 6.3 ESD#2 or later patch/upgrade to address the directory traversal vulnerability. If immediate patching is not possible, consider network-level restrictions to limit exposure of the EAServer management interfaces.

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
Appeon For PowerbuilderApplication
Affected:= 2.5= 2.6= 2.7= 2.8= 6.0= 6.1= 6.2= 6.5
EaserverApplication
Affected:= 5.0= 5.0.1= 5.1= 5.2= 5.2.1= 5.3= 5.5= 6.0= 6.0.2= 6.1= 6.2= 6.3
Replication ServerApplication
Affected:all versions= 15.2
Sybase WorkspaceApplication
Affected:all versions= 1.0= 1.5= 1.6= 1.7= 2.0= 2.0.1= 2.0.2= 2.1= 2.1.2= 2.5

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. Identify installed Sybase products
    Search system for EAServer, Appeon, Replication Server, or Workspace installations. Check for directories like C:\Sybase or /sybase, or look for running services with 'Sybase' in the name.
    Affected if Any of these Sybase products are found on the system
  2. Determine EAServer version
    Locate version information in the EAServer installation. Check the jaguar.cnf file, or run 'jaguar -version' from the bin directory, or look at the 'About EAServer' dialog in the management console.
    Affected if Version is 5.0, 5.0.1, 5.1, 5.2, 5.2.1, 5.3, 5.5, 6.0, 6.0.2, 6.1, 6.2, or 6.3 (before ESD#2)
  3. Determine Appeon version
    Check the Appeon installation directory or look for version info in Appeon-related files or registry entries under the Sybase folder.
    Affected if Version is 2.5, 2.6, 2.7, 2.8, 6.0, 6.1, 6.2, or 6.5
  4. Determine Workspace version
    Check the Sybase Workspace installation directory or look for version information in Workspace-related files or registry entries.
    Affected if Version is 1.0, 1.5, 1.6, 1.7, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.2, or 2.5, or the product is present with no specific version found
  5. Check if HTTP management interface is exposed
    Identify if the EAServer HTTP listener is enabled and accessible. Check the server configuration for HTTP port bindings (default port 8080 or 8088). Determine if the management console is reachable over the network.
    Affected if HTTP service is exposed to untrusted networks and the product version is in the affected list
  6. Verify Replication Server presence
    Check if Replication Server Messaging Edition (RSME) or Replication Server 15.2 is installed, looking in the Sybase installation directory.
    Affected if Replication Server (any version or specifically 15.2) is installed alongside EAServer

The environment is affected if any of the listed products are installed with versions matching the affected ranges AND the HTTP management interface is accessible, as the directory traversal flaw requires HTTP requests to be exploited.

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

Apply Sybase EAServer 6.3 ESD#2 or later patch/upgrade to address the directory traversal vulnerability. If immediate patching is not possible, consider network-level restrictions to limit exposure of the EAServer management interfaces.

Fix this in Appeon For Powerbuilder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-0497 — 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-2011-0497 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