dbcve.org
WebyastApplication · Suse

CVE-2012-0435

MEDIUM · 5.8 CVSS v2.0 Published 2013-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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
SUSE WebYaST before 1.2 0.2.63-0.6.1 allows remote attackers to modify the hosts list, and subsequently conduct man-in-the-middle attacks, via a crafted /host request on TCP port 4984.

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

SUSE WebYaST versions prior to 1.2 0.2.63-0.6.1 contain an unauthenticated vulnerability on TCP port 4984 where remote attackers can submit crafted /host requests to modify the hosts list. This host list manipulation can enable subsequent man-in-the-middle attacks.

MitigationUpgrade WebYaST to version 1.2 0.2.63-0.6.1 or later. If upgrade is not immediately possible, disable or restrict access to TCP port 4984 via firewall rules.

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
WebyastApplication
Affected:= 1.2

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

AV:N/AC:M/Au:N/C:P/I:P/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. Check if WebYaST is installed
    Look for the WebYaST package or service on the system using the system package manager or by checking for WebYaST processes
    Affected if WebYaST is present on the system
  2. Determine the installed WebYaST version
    Query the installed WebYaST package version using the system's package manager (rpm, zypper, etc.) or check the version reported by the WebYaST service
    Affected if The version is prior to 1.2 0.2.63-0.6.1 or cannot be determined to be at or above that version
  3. Check if TCP port 4984 is open and listening
    Use a network scanning tool (such as netstat, ss, nmap) to determine if port 4984 is in a listening state on any network interface
    Affected if Port 4984 is open and accepting connections
  4. Verify the /host endpoint is accessible
    Attempt to access http://<host>:4984/host or https://<host>:4984/host using a web request tool (curl, wget) without authentication
    Affected if The /host endpoint responds to requests without requiring authentication

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

Upgrade WebYaST to version 1.2 0.2.63-0.6.1 or later. If upgrade is not immediately possible, disable or restrict access to TCP port 4984 via firewall rules.

Fix this in Webyast Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

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