LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48193: Insecure Permissions vulnerability in JumpServer GPLv3 v.3.8.0 allows a remote attacker to execute arbitrar...

Insecure Permissions vulnerability in JumpServer GPLv3 v.3.8.0 allows a remote attacker to execute arbitrary code via bypassing the command filtering function. NOTE: this is disputed because command filtering is not intended to restrict what code can be run by authorized users who are allowed to execute files.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE alleges a JumpServer v3.8.0 command-filtering bypass that could let a remote attacker run arbitrary code. The record is disputed: the note says command filtering was not intended to limit code execution for authorized users already permitted to execute files. No CVSS, CWE, or authoritative affected-product metadata is provided.

Executive priority

Track this as an exposure-verification item, not an emergency patch event, unless JumpServer is internet-exposed or used to gate privileged administrative access. The dispute and missing severity prevent confident prioritization.

Technical view

The report frames the issue as insecure permissions in JumpServer GPLv3 v3.8.0, allowing arbitrary code execution by bypassing command filtering. The CVE note disputes vulnerability status because the control was not intended as an execution restriction for authorized file-execution users. The bundle provides no confirmed patch, mitigation, CVSS vector, or CWE.

Likely exposure

Potential exposure is limited to environments running the specifically named JumpServer GPLv3 v3.8.0, but the structured affected list is empty or n/a. Treat asset matching as a hypothesis requiring vendor confirmation.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. It includes a public bug write-up and GitHub issue reference, but the CVE itself is disputed, so exploitation relevance depends on local authorization boundaries and intended policy.

Researcher notes

Do not treat the command filter as a proven security boundary without vendor support. The key research question is whether an unauthorized or under-authorized user can gain execution beyond intended permissions. Public evidence in the bundle is incomplete and contested.

Mitigation direction

  • Inventory JumpServer deployments and identify any v3.8.0 GPLv3 instances.
  • Review JumpServer vendor guidance and issue 13394 before assuming a patch path.
  • Restrict file-execution privileges to users with a documented business need.
  • Audit command-filtering expectations against actual JumpServer security guarantees.
  • Monitor JumpServer release notes and security advisories for clarification.

Validation and detection

  • Confirm whether any deployed instance matches JumpServer GPLv3 v3.8.0.
  • Check whether command filtering is relied on as a security boundary.
  • Review user roles allowed to execute files through JumpServer.
  • Look for vendor statements resolving the dispute or naming fixed versions.
  • Record evidence gaps, including missing CVSS, CWE, and affected CPE data.
Prepared
Confidence
low
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-48193 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.