dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-31935

MEDIUM · 6.2 CVSS v3.1 Published 2025-04-11
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
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
Subnet Solutions PowerSYSTEM Center is affected by a mishandling of exceptional conditions vulnerability. Crafted data that is passed to the API may trigger an exception, resulting in a denial-of-service condition.

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

PowerSYSTEM Center API fails to properly handle exceptional conditions when processing crafted data input, causing an unhandled exception that results in denial of service. The vulnerability resides in the API layer where malformed requests trigger exceptions that are not caught, leading to service disruption.

MitigationImplement comprehensive exception handling and input validation across all API endpoints. Apply vendor patch when available and implement rate limiting/request validation as a defensive measure.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify PowerSYSTEM Center installation
    Search for PowerSYSTEM Center components on the system. Check for processes named 'powersystem', 'psc', or related API services. Look in common installation directories such as /opt/powersystem, C:\Program Files\PowerSYSTEM, or the application's installation path.
    Affected if PowerSYSTEM Center software is present on the system
  2. Determine installed version
    Locate version information in the installation directory. Check for version.txt, about dialog, or run the application's version command if available. Common paths include the application's root directory or /opt/powersystem/version
    Affected if Version cannot be determined or is unknown/older than current release
  3. Verify API component is enabled
    Check if the API layer is enabled in the application configuration. Look for API-related settings in config files (e.g., api.config, settings.xml) or examine the application's service status to confirm API services are running.
    Affected if API layer is exposed and accessible on the network
  4. Inspect API exception handling configuration
    Review API configuration files for existing exception handling mechanisms. Look for try-catch blocks in API code, error handling settings, or custom error pages. Check config files in the API directory for 'handleErrors', 'exceptionHandling', or similar settings.
    Affected if Exception handling is minimal, disabled, or not configured for API endpoints
  5. Test API resilience to malformed requests
    If authorized, send intentionally malformed API requests to endpoints and observe the response. Look for unhandled exception errors, stack traces in responses, or service disruptions. Monitor API service logs for uncaught exceptions when processing invalid input.
    Affected if Malformed requests cause unhandled exceptions or service disruption rather than graceful error responses

A user is affected if PowerSYSTEM Center is installed with its API layer enabled and the system exhibits unhandled exceptions or service disruption when processing malformed requests, indicating inadequate exception handling in the API.

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

Implement comprehensive exception handling and input validation across all API endpoints. Apply vendor patch when available and implement rate limiting/request validation as a defensive measure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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