CVE-2023-27283
Ibm Aspera Orchestrator 4.0.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-27283 is a medium-severity Observable Response Discrepancy (CWE-204) vulnerability in Ibm Aspera Orchestrator. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Security Appliances (T1590.006); 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 IA-6 (Authentication Feedback) and SI-11 (Error Handling) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-31061
Vulnerability Data
IBM Aspera Orchestrator 4.0.1 could allow a remote attacker to enumerate usernames due to observable response discrepancies. IBM X-Force ID: 248545.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
V13.4.5
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Obscuring authentication feedback directly stops one common source of observable response discrepancies.
Error handling explicitly requires messages that avoid revealing exploitable internal information.
Information flow enforcement can block responses that would otherwise disclose internal state to unauthorized parties.
Boundary protection monitors and filters outbound responses that could leak internal state.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent introduction of inconsistent response behavior that leaks internal state.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect observable response discrepancies before deployment.
Training developers about information disclosure through error messages reduces instances of CWE-204, since the weakness is often a knowledge gap (developer doesn't realize differing responses leak validity), but it is a specific implementation detail requiring careful coding practice that training alone does not guarantee, similar to the A.6.3 -> CWE-598 anchor.
Secure coding standards explicitly require uniform error handling to prevent information leakage.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; CWE-204 is a regular code-level weakness (different responses revealing internal state) that secure coding and testing practices partially prevent, and A.8.30 sits at its declared ceiling of `partial` on this verb.
Strong authentication reduces information leakage from authentication responses.