CVE-2008-4983

What it is

scilab-bin 4.1.2 allows local users to overwrite arbitrary files via a symlink attack on (a) /tmp/SciLink#####1, (b) /tmp/SciLink#####2, (c) /tmp/SciLink#####3, (d) /tmp/*.#####, (e) /tmp/*.#####.res, (f) /tmp/*.#####.err, and (g) /tmp/*.#####.diff temporary files, related to the (1) scilink, (2) scidoc, and (3) scidem scripts.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2008-11-06 15:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:58 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 6.9 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2008-11-06 15:55 UTC

Last modified

2026-06-16 22:58 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-59

Record status

Modified

Affected

• Scilab scilab-bin 4.1.2

Attack profile CVSS 2.0 · 6.9

Attack vector

Local

Complexity

Medium

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2008-4983.md and follow it. Check whether this project is affected by CVE-2008-4983. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge