How severe is CVE-2010-0219?

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

Which packages are affected by CVE-2010-0219?

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

How do I fix CVE-2010-0219?

No fixed release is recorded for CVE-2010-0219 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2010-0219 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2010-0219 actively exploited in the wild?

Yes. There are 7 known exploit references for CVE-2010-0219, including 3 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-2010-0219?

CVE-2010-0219 has an EPSS (Exploit Prediction Scoring System) score of 90.9%, 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.

What type of vulnerability is CVE-2010-0219?

CVE-2010-0219 is classified as CWE-255 (CWE-255). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2010-0219?

A Nuclei detection template exists for CVE-2010-0219, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2010-0219 published, and has it been updated?

CVE-2010-0219 was published on October 18, 2010 and was last updated on August 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2010-0219

CVE-2010-0219 is a CWE-255 vulnerability. 7 public exploit or proof-of-concept references are indexed, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Apache Axis2, as used in dswsbobje.war in SAP BusinessObjects Enterprise XI 3.2, CA ARCserve D2D r15, and other products, has a default password of axis2 for the admin account, which…

Published

Oct 18, 2010

Updated

Aug 7, 2024

Affected

2 products

Patched

See advisory

Exploits

7 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Apache Axis2, as used in dswsbobje.war in SAP BusinessObjects Enterprise XI 3.2, CA ARCserve D2D r15, and other products, has a default password of axis2 for the admin account, which makes it easier for remote attackers to execute arbitrary code by uploading a crafted web service.

Affected Products

2 products · 8 configurations

Application

axis2apache

7 versions

1.31.41.4.11.51.5.11.5.21.6

Application

businessobjectssap

1 version

3.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-16312remotemultiple✓ Verified

Axis2 - (Authenticated) Code Execution (via REST) (Metasploit)

by Metasploit · Dec 14, 2010

Exploit-DB Source

EDB-15869remotewindows✓ Verified

CA ARCserve D2D r15 - Web Service Servlet Code Execution

by rgod · Dec 30, 2010

Exploit-DB Source

EDB-16315remotemultiple✓ Verified

Axis2 / SAP BusinessObjects - (Authenticated) Code Execution (via SOAP) (Metasploit)

by Metasploit · Dec 14, 2010

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2010-0219 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2010-0219

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2010-0219 -u https://target

Template: Apache Axis2 Default Login
Severity: critical
Impact: Successful exploitation of this vulnerability can lead to unauthorized access to sensitive information or the ability to modify or delete data.
Remediation: Disable or restrict access to the Axis2 web interface, or apply the necessary patches or updates provided by the vendor.

Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-0219 in your dependencies?

Find it across your dependency tree, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2010-0219

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2010-0219

Frequently Asked Questions

Is CVE-2010-0219 in your dependencies?