CVE-2023-51906: An issue in yonyou YonBIP v3_23.05 allows a remote attacker to execute arbitrary code via a crafted script...
An issue in yonyou YonBIP v3_23.05 allows a remote attacker to execute arbitrary code via a crafted script to the ServiceDispatcherServlet uap.framework.rc.itf.IResourceManager component.
Security readout for executives and security teams
Plain-English summary
CVE-2023-51906 describes a critical remote code execution issue in yonyou YonBIP v3_23.05. An unauthenticated remote attacker may be able to run arbitrary code through the named ServiceDispatcherServlet/IResourceManager component. The source bundle does not identify a vendor patch, workaround, or confirmed active exploitation.
Executive priority
High priority for any organization running yonyou YonBIP v3_23.05. The reported impact is full system compromise without authentication, but remediation details are incomplete in the provided sources. Assign urgent ownership to validate exposure and obtain vendor guidance.
Technical view
The CVE reports arbitrary code execution via a crafted script to ServiceDispatcherServlet targeting uap.framework.rc.itf.IResourceManager. CVSS 3.1 is 9.8: network exploitable, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact. Affected CPE metadata is not populated.
Likely exposure
Organizations should check specifically for yonyou YonBIP v3_23.05 deployments, especially internet-facing or partner-accessible instances. Exposure cannot be reliably derived from CPE data because the bundle lists affected vendor, product, and versions as n/a despite the CVE description naming YonBIP.
Exploitation context
The bundle includes a public GitHub reference, but KEV is false and no provided source confirms active exploitation. Treat exploitability as serious because the CVSS vector indicates unauthenticated network access with low attack complexity, but do not assume real-world exploitation without additional evidence.
Researcher notes
Key gaps are missing CPEs, absent CWE mapping, no named fixed version, and no confirmed exploitation. The CVE description is specific enough to guide asset validation, but not enough to safely infer broader affected product lines or remediation steps.
Mitigation direction
Check yonyou guidance for affected builds, patches, and supported upgrade paths.
Restrict external access to YonBIP administrative and servlet endpoints where possible.
Prioritize upgrade or vendor-approved remediation for YonBIP v3_23.05.
Monitor application, web, and EDR telemetry for abnormal servlet requests or script execution.
Place exposed instances behind strong access controls while awaiting vendor guidance.
Validation and detection
Inventory all yonyou YonBIP deployments and confirm exact version numbers.
Identify whether any YonBIP v3_23.05 systems are internet-facing.
Review logs for unusual requests to ServiceDispatcherServlet and related resource manager components.
Confirm whether vendor advisories or support channels list fixed versions.
Verify compensating controls restrict unauthenticated access to affected application paths.
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.
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.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.