How severe is GHSA-99jg-r3f4-rpxj?

GHSA-99jg-r3f4-rpxj has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-99jg-r3f4-rpxj?

GHSA-99jg-r3f4-rpxj affects the following packages: afichet/openexr-viewer (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-99jg-r3f4-rpxj?

Update afichet/openexr-viewer to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-99jg-r3f4-rpxj is resolved across your whole dependency graph.

How do I detect GHSA-99jg-r3f4-rpxj in my GitHub Actions dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for afichet/openexr-viewer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-99jg-r3f4-rpxj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-99jg-r3f4-rpxj?

O3 pinpoints whether GHSA-99jg-r3f4-rpxj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-99jg-r3f4-rpxj actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-99jg-r3f4-rpxj, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-99jg-r3f4-rpxj?

GHSA-99jg-r3f4-rpxj has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 60th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-99jg-r3f4-rpxj?

GHSA-99jg-r3f4-rpxj is classified as CWE-120 (CWE-120). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-99jg-r3f4-rpxj published, and has it been updated?

GHSA-99jg-r3f4-rpxj was published on December 12, 2023 and was last updated on December 12, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 GitHub Actions

GHSA-99jg-r3f4-rpxj

CRITICAL

memory overflow vulnerability in OpenEXR-viewer

Also known asCVE-2023-50245

Published

Dec 12, 2023

Updated

Dec 12, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk60th percentile-2.27%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦afichet/openexr-viewer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.

Description

Just open this exr file through openexr-viewer.

( poc send by email )

This is windbg log file.

[ POC 2 ] (8660.7e44): Access violation - code c0000005 (!!! second chance !!!) openexr_viewer+0x27be4: 00007ff713ff7be4 c744880c0000803f mov dword ptr [rax+rcx*4+0Ch],3F800000h ds:0000020a3ac8000c=????????

Attempt to write the value 1.0 to the memory address 0x20A3AC8000C

[ POC 1 ] (1404.9264): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. openexr_viewer+0x27be4: 00007ff713ff7be4 c744880c0000803f mov dword ptr [rax+rcx*4+0Ch],3F800000h ds:0000029cb371600c=????????

Attempt to write the value 1.0 to the memory address 0x29CB371600C

Credits Team : ZeroPointer 이동하 ( Lee Dong Ha of ZeroPointer Lab ) 정지민 ( Jeong Jimin of ZeroPointer Lab ) 박우진 ( Park Woojin of ZeroPointer Lab ) 전우진 ( Jeon Woojin of ZeroPointer Lab )

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`afichet/openexr-viewer`	all versions	0.6.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OpenEXR-viewer is a viewer for OpenEXR files with detailed metadata prob…

github.comNVDDec 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for afichet/openexr-viewer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update afichet/openexr-viewer to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-99jg-r3f4-rpxj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-99jg-r3f4-rpxj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-99jg-r3f4-rpxj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Just open this exr file through openexr-viewer. ( poc send by email ) This is windbg log file. [ POC 2 ] (8660.7e44): Access violation - code c0000005 (!!! second chance !!!) openexr_viewer+0x27be4: 00007ff7`13ff7be4 c744880c0000803f mov dword ptr [rax+rcx*4+0Ch],3F800000h ds:0000020a`3ac8000c=???????? Attempt to write the value 1.0 to the memory address 0x20A3AC8000C [ POC 1 ] (1404.9264): Access violation - code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. openexr_viewer+0x27be4: 00007ff7`13ff

O3 Security · Impact-Aware SCA

Is GHSA-99jg-r3f4-rpxj in your dependencies?

O3 detects GHSA-99jg-r3f4-rpxj across GitHub Actions dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works