dbcve.org
Database LiteDatabase / datastore · Oracle

CVE-2013-0361

HIGH · 10.0 CVSS v2.0 Published 2013-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the Mobile Server component in Oracle Database Mobile/Lite Server (formerly Oracle Database Lite) 10.3.0.3 and 11.1.0.0 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors, a different vulnerability than CVE-2013-0366.

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 · moderate confidence

Critical vulnerability in Oracle Database Mobile/Lite Server's Mobile Server component affecting versions 10.3.0.3 and 11.1.0.0. The vulnerability is remotely exploitable without authentication and provides complete compromise of confidentiality, integrity, and availability. Specific technical details are not disclosed (unspecified with unknown attack vectors).

MitigationApply Oracle Critical Patch Update for January 2013 or later. If the product is end-of-life, consider migration to supported Oracle mobile server solutions or network segmentation to limit exposure.

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
Database LiteDatabase / datastore
Affected:= 10.3.0.3
Database Mobile\/lite ServerDatabase / datastore
Affected:= 10.3.0.3= 11.1.0.0

CVSS 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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Oracle Database Lite/Mobile Server installation
    Check for Oracle Database Lite installation directories such as ORACLE_HOME/mobile or ORACLE_HOME/mobilelite, or look for the 'mobile' or 'mdk' services on the system. On Windows, check Program Files for Oracle directories containing 'Lite' or 'Mobile Server'. On Linux/Unix, common paths include $ORACLE_HOME/mobile or /opt/oracle/mobile_lite.
    Affected if Oracle Database Lite or Mobile Server software is present on the system.
  2. Determine installed Mobile Server version
    Locate the Mobile Server component version file. For Oracle Database Lite 10g, check $ORACLE_HOME/mobile/server.properties or $ORACLE_HOME/mobile/version.txt. For Oracle Database Mobile Server 11g, check $ORACLE_HOME/mobile_lite/mobile/server.ini or the installation inventory file under $ORACLE_HOME/inventory/ComponentsDirectory/oracle.mobile.lite.
    Affected if The installed version matches exactly 10.3.0.3 or 11.1.0.0.
  3. Check Mobile Server component status
    Identify whether the Mobile Server component is configured and running. Look for processes named 'mobileserver', 'mdk', or 'sync' in the process list, or check for Mobile Server listener ports (typically 8080, 8888, or 9090). On Windows, check Windows Services for 'Oracle Database Lite' or 'Oracle Mobile Server' services with Running status.
    Affected if The Mobile Server component is installed and the service is running or enabled.
  4. Verify network exposure of Mobile Server
    Check network configuration files (listener.ora, sqlnet.ora) or firewall rules to determine if the Mobile Server ports are exposed to network access. Review any IP bindings or ACL configurations that permit external access to the Mobile Server HTTP listener.
    Affected if Mobile Server is accessible over the network without authentication requirements.

A system is affected if Oracle Database Lite 10.3.0.3 or Oracle Database Mobile/Lite Server 11.1.0.0 is installed with the Mobile Server component running and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update for January 2013 or later. If the product is end-of-life, consider migration to supported Oracle mobile server solutions or network segmentation to limit exposure.

Fix this in Database Lite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0361 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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