M Business AnywhereApplication · Sybase

CVE-2011-5078

MEDIUM · 6.5 CVSS v2.0 Published 2012-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The web administration interface in the server in Sybase M-Business Anywhere 6.7 before ESD# 3 and 7.0 before ESD# 7 does not require admin authentication for unspecified scripts, which allows remote authenticated users to list or delete user accounts, modify passwords, or read log files via HTTP requests, aka Bug IDs 678497 and 678499.

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

The web administration interface in Sybase M-Business Anywhere 6.7 (before ESD#3) and 7.0 (before ESD#7) fails to enforce admin-level authentication on certain scripts. Authenticated users can send HTTP requests to perform privileged operations including listing/deleting user accounts, modifying passwords, and reading log files.

MitigationApply vendor patches (ESD#3 for v6.7 or ESD#7 for v7.0) to enforce proper admin authentication on admin scripts. If patching is not immediately feasible, restrict network access to the web admin interface using firewall rules or network segmentation.

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
M Business AnywhereApplication
Affected:= 6.7= 7.0

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 the installed Sybase M-Business Anywhere version
    Check the product version displayed in the web administration interface login page, or query the server documentation/configuration files for the installed build number. Compare against version 6.7 or 7.0.
    Affected if The installed version is 6.7 or 7.0 (or any version between these releases) and has not had ESD#3 (for 6.7) or ESD#7 (for 7.0) applied.
  2. Confirm the web administration interface is accessible
    Attempt to access the web admin URL for Sybase M-Business Anywhere (typically on ports 80/443 or configured ports). Verify the interface responds with a login page.
    Affected if The web admin interface is exposed and reachable on the network.
  3. Verify admin authentication is enforced on privileged operations
    Log in with a non-administrator user account and attempt to access or execute admin-level functions such as user account management, password modifications, or log file viewing via direct HTTP requests. Observe whether these requests succeed without requiring admin-level credentials.
    Affected if Non-admin users can successfully perform privileged operations (listing/deleting users, modifying passwords, reading logs) without receiving an authentication error.

You are affected if you are running version 6.7 or 7.0 of Sybase M-Business Anywhere without the corresponding ESD patches and the web admin interface allows authenticated non-admin users to execute privileged admin functions.

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 vendor patches (ESD#3 for v6.7 or ESD#7 for v7.0) to enforce proper admin authentication on admin scripts. If patching is not immediately feasible, restrict network access to the web admin interface using firewall rules or network segmentation.

Fix this in M Business Anywhere Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-5078 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