dbcve.org
MoveitApplication

CVE-2023-30394

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The MoveIt framework 1.1.11 for ROS allows cross-site scripting (XSS) via the API authentication function. NOTE: this issue is disputed by the original reporter because it has "no impact."

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

Cross-site scripting (XSS) vulnerability in MoveIt framework 1.1.11 for ROS, specifically in the API authentication function. This allows injection of malicious scripts through authentication parameters.

MitigationImplement input validation and output encoding on authentication function parameters; deploy Content Security Policy (CSP) headers to mitigate XSS execution.

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
MoveitApplication
Affected:= 1.1.11

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 MoveIt installation and version
    Run 'rosversion moveit' or 'rospack find moveit' to locate the package, then check the package.xml for the version field
    Affected if The installed version is exactly 1.1.11
  2. Check for MoveIt web/API interfaces
    Search for configuration files related to MoveIt web serving or API endpoints in /opt/ros/*/share/moveit/ and any user workspace configs
    Affected if MoveIt includes a web interface or API server that exposes authentication functions
  3. Inspect authentication module configuration
    Look for configuration files in the MoveIt package that define API authentication parameters or endpoints
    Affected if Authentication parameters can be passed through HTTP requests to MoveIt API endpoints
  4. Examine running ROS nodes for web services
    Run 'rosnode list' and check for any nodes related to web serving, moveit_api, or similar services; also check running processes for any HTTP servers
    Affected if A web service node is running that handles MoveIt authentication requests
  5. Review ROS parameter server for MoveIt settings
    Run 'rosparam list | grep moveit' to see if any MoveIt-related parameters expose API or authentication settings
    Affected if MoveIt authentication parameters are exposed through the ROS parameter server

The environment is affected if MoveIt version 1.1.11 is installed AND any web/API interface for authentication is enabled or 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding on authentication function parameters; deploy Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Moveit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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