Online WeatherApplication · Iblsoft

CVE-2020-9407

MEDIUM · 5.3 CVSS v3.1 Published 2020-02-26
Fix available
A fix is available. Upgrade to 4.3.5 or later.
See remediation →
62/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
IBL Online Weather before 4.3.5a allows attackers to obtain sensitive information by reading the IWEBSERVICE_JSONRPC_COOKIE cookie.

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 · moderate confidence

IBL Online Weather before version 4.3.5a stores sensitive information in the IWEBSERVICE_JSONRPC_COOKIE cookie, which can be read by attackers to obtain potentially sensitive data such as session tokens or credentials.

MitigationUpgrade IBL Online Weather to version 4.3.5a or later to remediate the vulnerability; until then, consider monitoring or restricting access to endpoints that return this cookie.

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
Online WeatherApplication
Affected:< 4.3.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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the installed version of IBL Online Weather
    Locate the application version in the software itself, typically found in the About section, version file, or header of the main interface
    Affected if The version is displayed as less than 4.3.5a (for example, 4.3.4, 4.3.0, or any version prior to 4.3.5)
  2. Confirm the presence of the IWEBSERVICE_JSONRPC_COOKIE cookie
    Inspect browser developer tools (Application/Storage tab) or capture HTTP traffic to identify if the IWEBSERVICE_JSONRPC_COOKIE is being set by the application
    Affected if The cookie named IWEBSERVICE_JSONRPC_COOKIE is present in the response headers or browser storage
  3. Examine cookie contents for sensitive data
    Decode the cookie value (it may be Base64 or otherwise encoded) and inspect whether it contains credentials, session tokens, user identifiers, or other sensitive information
    Affected if The decoded cookie value reveals plaintext or encoded sensitive data such as usernames, passwords, session IDs, or authentication tokens
  4. Verify authentication mechanism
    Check the application configuration or documentation to determine if user authentication is required and if the cookie is used to store authentication state
    Affected if The application uses authentication and the IWEBSERVICE_JSONRPC_COOKIE cookie is involved in maintaining authenticated sessions
  5. Review application configuration for cookie security settings
    Inspect the application's cookie configuration or HTTP response headers to check if HttpOnly, Secure, or SameSite attributes are properly set on the IWEBSERVICE_JSONRPC_COOKIE
    Affected if The cookie lacks appropriate security flags (HttpOnly, Secure) or contains sensitive data without proper protection

You are affected if IBL Online Weather is installed at a version below 4.3.5a and the IWEBSERVICE_JSONRPC_COOKIE cookie is present and contains sensitive data such as credentials or session tokens.

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
Upgrade available Upgrade to 4.3.5 or later
Fixed in 4.3.5
Interim mitigation

Upgrade IBL Online Weather to version 4.3.5a or later to remediate the vulnerability; until then, consider monitoring or restricting access to endpoints that return this cookie.

Fix this in Online Weather Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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