CVE-2013-1495
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedasr in Oracle Auto Service Request in Oracle Support Tools before 4.3.2 allows local users to modify arbitrary files via a symlink attack on a predictable filename in /tmp.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA symlink attack vulnerability in the asr component of Oracle Auto Service Request (Oracle Support Tools) versions before 4.3.2 allows local users to modify arbitrary files on the system by exploiting a predictable temporary filename in /tmp.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Oracle Auto Service Request is installedLook for the Oracle ASR installation directory or check for the 'asr' component in Oracle inventory files. Common locations: $ORACLE_HOME/asr or /opt/oracle/asr. On Windows, check Program Files for Oracle Auto Service Request.Affected if Oracle Auto Service Request software is present on the system
-
Determine the installed ASR versionRun the ASR version command or check the version file in the ASR installation directory. Typical command: 'asr version' or inspect version.info, oradomain.xml, or similar metadata files in the ASR home directory.Affected if Installed version is lower than 4.3.2 (versions before the fix)
-
Verify /tmp directory permissionsRun 'ls -ld /tmp' to check if the /tmp directory is world-writable (permissions should not be 'drwxrwxrwt'). The vulnerability requires /tmp to be world-writable for the symlink attack to succeed.Affected if The /tmp directory has world-writable permissions (mode 1777 or similar open permissions)
-
Inspect /tmp for suspicious symlinks with predictable ASR-related namesList files in /tmp that may be created by ASR, looking for predictable temporary filenames or symlinks (e.g., files named with patterns like 'asr_tmp_*' or similar temporary file constructs). Use 'ls -la /tmp | grep -i asr'.Affected if Symlinks or temporary files exist in /tmp that point to sensitive system locations and were created by the ASR process
You are affected if Oracle Auto Service Request is installed with a version before 4.3.2 AND the /tmp directory retains world-writable permissions, allowing the symlink attack to succeed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Oracle Auto Service Request to version 4.3.2 or later which addresses the symlink vulnerability. As a compensating control, restrict or eliminate world-writable permissions on /tmp to reduce the attack surface.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1495 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1495 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data