CVE-2010-3575
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 · uneditedUnspecified vulnerability in the Oracle Communications Messaging Server (Sun Java System Messaging Server) component in Oracle Sun Products Suite 6.0, 6.2, 6.3, and 7.0 allows remote attackers to affect confidentiality and integrity via unknown vectors related to Web Mail.
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 confidenceCVE-2010-3575 is an unspecified vulnerability in the Oracle Communications Messaging Server (formerly Sun Java System Messaging Server) Web Mail component affecting versions 6.0, 6.2, 6.3, and 7.0. The vulnerability allows remote unauthenticated attackers to impact confidentiality and integrity through unknown vectors in the web mail interface.
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= 6.0= 6.2= 6.3= 7.0CVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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.
-
Identify if Messaging Server is installedLook for Oracle Communications Messaging Server or Sun Java System Messaging Server processes or installation directories on the system. Common locations include /opt/SUNWmsgsr or product-specific directories.Affected if The product is not installed or not one of these two product names
-
Check the installed versionRun the version command or check the product version file. For Sun Java System Messaging Server, this is often obtainable via 'msver' command or checking version information in the installation directory.Affected if The installed version is exactly 6.0, 6.2, 6.3, or 7.0
-
Verify Web Mail component is enabledCheck the Messaging Server configuration for web mail service. Look for webmail or HTTP service configuration files (typically in the config directory under msconfig or similar). Confirm the webmail service is configured and not disabled.Affected if Web Mail (HTTP/HTTPS service for messaging) is enabled in the configuration
-
Check network exposure of web mail interfaceIdentify the port used by the web mail interface (commonly ports 80, 443, 8080, or 8443). Use 'netstat' or 'ss' commands to determine if these ports are listening on external interfaces (0.0.0.0) rather than localhost only.Affected if The web mail HTTP/HTTPS port is listening on a publicly accessible network interface
A user is affected if they have Oracle Communications Messaging Server or Sun Java System Messaging Server version 6.0, 6.2, 6.3, or 7.0 running with the Web Mail component enabled and exposed to network access.
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 dataApply Oracle Critical Patch Update patches for this vulnerability; if patches are unavailable for these legacy versions, upgrade to a supported Oracle Communications Messaging Server release or implement network access controls restricting web mail exposure to trusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3575 — 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-2010-3575 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