CVE-2010-3380
UnknownEPSS 0.30%
Last modified
CVE-2010-3380 is a vulnerability of currently unknown severity. The (1) init.d/slurm and (2) init.d/slurmdbd scripts in SLURM before 2.1.14 place the . (dot) directory in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
Description
The (1) init.d/slurm and (2) init.d/slurmdbd scripts in SLURM before 2.1.14 place the . (dot) directory in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Llnl | Slurm | <= 2.1.13 |
| Llnl | Slurm | 1.3.10 |
| Llnl | Slurm | 1.3.11 |
| Llnl | Slurm | 1.3.12 |
| Llnl | Slurm | 1.3.13 |
| Llnl | Slurm | 1.3.14 |
| Llnl | Slurm | 1.3.15 |
| Llnl | Slurm | 2.0.0 |
| Llnl | Slurm | 2.0.1 |
| Llnl | Slurm | 2.0.2 |
| Llnl | Slurm | 2.0.3 |
| Llnl | Slurm | 2.0.4 |
| Llnl | Slurm | 2.0.5 |
| Llnl | Slurm | 2.0.6 |
| Llnl | Slurm | 2.0.7 |
| Llnl | Slurm | 2.0.8 |
| Llnl | Slurm | 2.0.9 |
| Llnl | Slurm | 2.1.0 |
| Llnl | Slurm | 2.1.1 |
| Llnl | Slurm | 2.1.2 |
| Llnl | Slurm | 2.1.4 |
| Llnl | Slurm | 2.1.5 |
| Llnl | Slurm | 2.1.6 |
| Llnl | Slurm | 2.1.7 |
| Llnl | Slurm | 2.1.8 |
| Llnl | Slurm | 2.1.9 |
| Llnl | Slurm | 2.1.10 |
| Llnl | Slurm | 2.1.11 |
| Llnl | Slurm | 2.1.12 |
References
- http://secunia.com/advisories/41614Vendor Advisory
- http://secunia.com/advisories/41614Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2010-3380?
The (1) init.d/slurm and (2) init.d/slurmdbd scripts in SLURM before 2.1.14 place the . (dot) directory in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.
How severe is CVE-2010-3380?
Severity scoring for CVE-2010-3380 is pending analysis. The EPSS model estimates a 0.30% probability of exploitation in the next 30 days.
How do I fix CVE-2010-3380?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2010
- CVE-2010-3373paxtest handles temporary files insecurely5.5
- CVE-2010-3374Qt Creator before 2.0.1 places a zero-length directory name …
- CVE-2010-3375qtparted has insecure library loading which may allow arbitr…9.8
- CVE-2010-3376The (1) proofserv, (2) xrdcp, (3) xrdpwdadmin, and (4) xrd s…
- CVE-2010-3377The (1) runSalome, (2) runTestMedCorba, (3) runLightSalome, …
- CVE-2010-3378The (1) scilab, (2) scilab-cli, and (3) scilab-adv-cli scrip…
- CVE-2010-3381The (1) tangerine and (2) tangerine-properties scripts in Ta…
- CVE-2010-3382tauex in Tuning and Analysis Utilities (TAU) 2.16.4 places a…
- CVE-2010-3383The (1) teamspeak and (2) teamspeak-server scripts in TeamSp…
- CVE-2010-3384The (1) torcs, (2) nfsperf, (3) accc, (4) texmapper, (5) tra…
- CVE-2010-3385TuxGuitar 1.2 places a zero-length directory name in the LD_…
- CVE-2010-3386usttrace in LTTng Userspace Tracer (aka UST) 0.7 places a ze…
Are you affected by CVE-2010-3380?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST