How severe is CVE-2016-0492?

No CVSS score has been assigned to CVE-2016-0492 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2016-0492?

Affected package information for CVE-2016-0492 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2016-0492?

No patch has shipped for CVE-2016-0492 yet — track the oracle application testing suite advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2016-0492 across my infrastructure?

Inventory every oracle application testing suite deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2016-0492 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2016-0492?

O3 detects and blocks CVE-2016-0492 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2016-0492 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2016-0492, including 2 documented proof-of-concept exploits on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-0492?

CVE-2016-0492 has an EPSS (Exploit Prediction Scoring System) score of 92.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Which products and versions are affected by CVE-2016-0492?

CVE-2016-0492 affects oracle application testing suite (2 versions, e.g. 12.4.0.2, 12.5.0.2). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2016-0492 published, and has it been updated?

CVE-2016-0492 was published on January 21, 2016 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2016-0492

Unspecified vulnerability in the Oracle Application Testing Suite component in Oracle Enterprise Manager Grid Control 12.4.0.2 and 12.5.0.2 allows remote attackers to affect confidentiality…

Published

Jan 21, 2016

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

92.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Unspecified vulnerability in the Oracle Application Testing Suite component in Oracle Enterprise Manager Grid Control 12.4.0.2 and 12.5.0.2 allows remote attackers to affect confidentiality and integrity via unknown vectors related to Load Testing for Web Apps, a different vulnerability than CVE-2016-0488. NOTE: the previous information is from the January 2016 CPU. Oracle has not commented on third-party claims that this is a directory traversal vulnerability in the isAllowedUrl function, which allows remote attackers to bypass authentication via directory traversal sequences following a URI entry that does not require authentication, as demonstrated by olt/Login.do/../../olt/UploadFileUpload.do.

Affected Products

1 product · 2 configurations

Application

application testing suiteoracle

2 versions

12.4.0.212.5.0.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-39691webappsjsp✓ Verified

Oracle Application Testing Suite (ATS) 12.4.0.2.0 - Authentication Bypass / Arbitrary File Upload

by Zhou Yu · Apr 13, 2016

Exploit-DB Source

EDB-39852remotejava✓ Verified

Oracle Application Testing Suite (ATS) - Arbitrary File Upload (Metasploit)

by Metasploit · May 25, 2016

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every oracle application testing suite deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2016-0492 yet — track the oracle application testing suite advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2016-0492 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2016-0492. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2016-0492 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2016-0492 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2016-0492

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2016-0492 being exploited in your environment?