dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-62193

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Sites running NOAA PMEL Live Access Server (LAS) are vulnerable to remote code execution via specially crafted requests that include PyFerret expressions. By leveraging a SPAWN command, a remote, unauthenticated attacker can execute arbitrary OS commands. Fixed in a version of 'gov.noaa.pmel.tmap.las.filter.RequestInputFilter.java' from 2025-09-24.

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 NOAA PMEL Live Access Server contains a critical remote code execution vulnerability in the RequestInputFilter.java component. Attackers can inject malicious PyFerret expressions through specially crafted HTTP requests that trigger the SPAWN command, allowing execution of arbitrary operating system commands without authentication. The CVSS 9.8 score indicates trivial exploitability with potential for complete system compromise.

MitigationImmediately update gov.noaa.pmel.tmap.las.filter.RequestInputFilter.java to the patched version from 2025-09-24 or later. As an interim control, restrict network access to the LAS service until the patch can be applied.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate the Live Access Server installation
    Search for files named 'RequestInputFilter.java' or directories containing 'las' or 'LiveAccessServer' in the application root. Check common deployment paths such as /opt/las, /var/www/las, or the application server's webapps directory.
    Affected if The file or LAS application is found and the RequestInputFilter.java component exists in the environment.
  2. Determine the RequestInputFilter.java version or patch date
    Inspect the RequestInputFilter.java file for version comments, or check the file modification timestamp. The patched version was released on 2025-09-24. Compare the file's last modification date against this patch date.
    Affected if The file exists with a modification date before 2025-09-24, or no patch date/version information is present indicating it predates the fix.
  3. Identify if the LAS service is network-exposed
    Review network configuration files (e.g., server.xml, web.xml, firewall rules) or use netstat/ss commands to check if the LAS HTTP service listens on a non-localhost interface (0.0.0.0 or public IP).
    Affected if The LAS service is listening on a reachable network interface (0.0.0.0 or external IP) rather than only localhost (127.0.0.1).
  4. Check for PyFerret SPAWN command usage in request handling
    Examine the RequestInputFilter.java source code for code handling PyFerret expressions or SPAWN commands. Look for unvalidated input paths that could accept user-supplied expressions.
    Affected if The code contains unsanitized input handling for PyFerret expressions or SPAWN command processing without proper validation.
  5. Review access logs for suspicious LAS requests
    Search HTTP access logs for unusual patterns such as requests containing PyFerret syntax, SPAWN keywords, or shell metacharacters in parameters that might indicate exploitation attempts.

A user is affected if the RequestInputFilter.java component exists in their environment with a modification date before 2025-09-24 (or unknown/older version) AND the LAS service is network-accessible.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Immediately update gov.noaa.pmel.tmap.las.filter.RequestInputFilter.java to the patched version from 2025-09-24 or later. As an interim control, restrict network access to the LAS service until the patch can be applied.

Recommended fix High confidence

Commit de5f9237bfd4ac5085bcc49a6e30bbc9507ddb29 (or a release version dated 2025-09-24 or later containing this fix)

  1. 1. Navigate to the NOAA PMEL LAS repository: https://github.com/NOAA-PMEL/LAS
  2. 2. Locate the file 'gov.noaa.pmel.tmap.las.filter.RequestInputFilter.java' in the source tree
  3. 3. Review commit de5f9237bfd4ac5085bcc49a6e30bbc9507ddb29 to identify the specific code changes that address the OS command injection vulnerability
  4. 4. Apply the same fix to your local copy of the file - this should involve sanitizing or removing the PyFerret SPAWN command execution path that allows unauthenticated remote code execution
  5. 5. Rebuild the LAS application with the patched filter class
  6. 6. Redeploy the updated WAR/JAR file to your application server
  7. 7. Verify the patch by testing that PyFerret expressions can no longer execute arbitrary OS commands

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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