dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-1077

CRITICAL · 9.5 CVSS v4.0 Published 2025-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A security vulnerability has been identified in the IBL Software Engineering Visual Weather and derived products (NAMIS, Aero Weather, Satellite Weather). The vulnerability is present in the Product Delivery Service (PDS) component in specific server configurations where the PDS pipeline utilizes the IPDS pipeline with Message Editor Output Filters enabled. A remote unauthenticated attacker can exploit this vulnerability to send unauthenticated requests to execute the IPDS pipeline with specially crafted Form Properties, enabling remote execution of arbitrary Python code. This vulnerability could lead to a full system compromise of the affected server, particularly if Visual Weather services are run under a privileged user account—contrary to the documented installation best practices. Upgrade to the patched versions 7.3.10 (or higher), 8.6.0 (or higher).

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

A remote code execution vulnerability exists in IBL Software Engineering Visual Weather's Product Delivery Service (PDS) when using IPDS pipeline with Message Editor Output Filters. Unauthenticated attackers can send specially crafted Form Properties to execute arbitrary Python code, leading to full system compromise.

MitigationUpgrade Visual Weather and derived products (NAMIS, Aero Weather, Satellite Weather) to version 7.3.10+ or 8.6.0+ to patch the arbitrary Python code execution vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Visual Weather product
    Locate the Visual Weather, NAMIS, Aero Weather, or Satellite Weather installation directory and check for version information in the application or license files
    Affected if Any of these products are installed with version below 7.3.10 or below 8.6.0
  2. Verify Product Delivery Service (PDS) is running
    Check if the PDS executable or service is running on the system using task manager or service management tools
    Affected if PDS is active and the Visual Weather version is vulnerable
  3. Confirm IPDS pipeline is enabled
    Inspect the PDS configuration files for IPDS pipeline settings, typically in the PDS config directory
    Affected if IPDS pipeline is configured and the version is below the fixed releases
  4. Check Message Editor Output Filters configuration
    Examine PDS configuration for Message Editor Output Filter settings within the IPDS pipeline configuration
    Affected if Message Editor Output Filters are enabled in the IPDS pipeline on a vulnerable version

The environment is affected if Visual Weather or derived products (NAMIS, Aero Weather, Satellite Weather) are installed with version below 7.3.10 or below 8.6.0, and the Product Delivery Service is running with IPDS pipeline and Message Editor Output Filters enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Visual Weather and derived products (NAMIS, Aero Weather, Satellite Weather) to version 7.3.10+ or 8.6.0+ to patch the arbitrary Python code execution vulnerability.

Recommended fix High confidence

7.3.10 or higher (for v7.x), 8.6.0 or higher (for v8.x)

  1. Back up the current Visual Weather installation and configuration before upgrading
  2. Download the patched version (7.3.10 or higher for version 7.x, or 8.6.0 or higher for version 8.x) from IBL Software Engineering
  3. Install the patched version following the vendor's standard upgrade procedure
  4. After upgrading, verify that the Product Delivery Service (PDS) starts successfully
  5. Review server configuration to ensure Visual Weather services do NOT run under a privileged user account (e.g., root or Administrator), as this contradicts documented installation best practices
  6. Confirm that the IPDS pipeline with Message Editor Output Filters is properly secured or disabled if not required
Caveat No explicit breaking changes documented for this security upgrade; however, configuration review is recommended to enforce best practices

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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