Security Resilience

CVE-2023-50327

Ibm Powersc 1.3 … 2.1

Published
02 February 2024
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0049 41th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-50327 is a medium-severity Trusting HTTP Permission Methods on the Server Side (CWE-650) vulnerability in Ibm Powersc. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

IBM PowerSC 1.3, 2.0, and 2.1 uses insecure HTTP methods which could allow a remote attacker to perform unauthorized file request modification. IBM X-Force ID: 275109.

CWE(s)
CWE-650CWE-436

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
attack.mitre.org →
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
attack.mitre.org →
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-50933Same product: Ibm Powersc
CVE-2023-50328Same product: Ibm Powersc
CVE-2023-50935Same product: Ibm Powersc
CVE-2023-50936Same product: Ibm Powersc
CVE-2023-50326Same product: Ibm Powersc
CVE-2023-50941Same product: Ibm Powersc
CVE-2023-50940Same product: Ibm Powersc
CVE-2023-50962Same product: Ibm Powersc
CVE-2023-50934Same product: Ibm Powersc
CVE-2023-50938Same product: Ibm Powersc

Affected Assets

ibm
powersc
1.3, 2.0, 2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.1
  • V3.5.3
  • V4.1.4

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

AC-3 enforces authorizations for resource access without permitting unsafe assumptions about request methods to bypass checks.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover cases where two products interpret the same inputs or state transitions differently.

SI-10 Information Input Validation good match

Strict, consistently applied input validation reduces the chance that one product will accept data the other product rejects or interprets differently.

SA-8 Security and Privacy Engineering Principles partial match

Applying security engineering principles during design can require unambiguous protocol and data-format specifications that eliminate divergent interpretations between products.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover this server-side logic flaw through testing or scanning.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent flawed assumptions about HTTP method safety during design and coding.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates a secure SDLC process with checkpoints, secure coding, testing and training; it does not stop differing interpretations of shared state or inputs between two products from arising or being exploited

A.8.26 Application security requirements partial match
blocks

Application security requirements can mandate proper HTTP method usage and state-changing operation restrictions.

A.8.27 Secure system architecture and engineering principles partial match
blocks

Secure system architecture principles include proper HTTP method handling and RESTful design to prevent state changes via GET.

A.8.28 Secure coding partial match
prevents

Secure coding practices directly address improper HTTP method usage and ensure state-changing operations use POST/PUT/DELETE.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect and prevent vulnerabilities where GET requests cause unintended state changes.

A.8.8 Management of technical vulnerabilities partial match
removes

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-436, a class-level weakness, and none of its children carries one either.

References