GHSA-fwhj-785h-43hh: OliveTin has crash on NPE by calling APIs with invalid bindings or log references
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/OliveTin/OliveTin (Go) 0.0.0-20260304225158-bb14c5da3e64.
Low priority for now. Upgrade to github.com/OliveTin/OliveTin (Go) 0.0.0-20260304225158-bb14c5da3e64 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### Summary 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: ```bash 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) ``` ### Impact 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.
- Published
- Mar 5, 2026
- Updated
- Mar 23, 2026
- EPSS
- —
- CWE
- CWE-20
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/OliveTin/OliveTin | pkg:golang/github.com/OliveTin/OliveTin |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/OliveTin/OliveTin | before 0.0.0-20260304225158-bb14c5da3e64 | 0.0.0-20260304225158-bb14c5da3e64 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GO-2026-4687OliveTin's email argument makes compliance harder, enables log injection in github.com/OliveTin/OliveTin0Monitor
- GHSA-xx6g-43w2-9g6gOliveTin's email argument makes compliance harder, enables log injection0Monitor
- GO-2026-4621OliveTin has crash on NPE by calling APIs with invalid bindings or log references in github.com/OliveTin/OliveTin0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/OliveTin/OliveTin | 0.0.0-20260304225158-bb14c5da3e64 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.