CVE-1999-1368
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 · uneditedAV Option for MS Exchange Server option for InoculateIT 4.53, and possibly other versions, only scans the Inbox folder tree of a Microsoft Exchange server, which could allow viruses to escape detection if a user's rules cause the message to be moved to a different mailbox.
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 confidenceThe InoculateIT antivirus plugin for Microsoft Exchange Server only monitors and scans messages within the Inbox folder tree. If users have configured mailbox rules that automatically move incoming messages to other folders or mailboxes, those messages completely bypass antivirus scanning, allowing malware to evade detection.
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.53CVSS 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
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Verify InoculateIT antivirus installation and versionCheck installed programs or antivirus software inventory for Broadcom InoculateIT version 4.53. On the Exchange Server, review the installed software list or antivirus console to confirm the exact version number.Affected if The installed version is exactly 4.53 of Broadcom InoculateIT antivirus software.
-
Confirm InoculateIT Exchange plugin is presentLocate the InoculateIT plugin or component specifically designed for Microsoft Exchange Server. Check the antivirus management console or installed Exchange server extensions for the InoculateIT scanning component.Affected if The InoculateIT Exchange Server plugin or scanner component is installed and active on the mail server.
-
Review folder scanning configurationAccess the InoculateIT configuration settings for the Exchange plugin. Look for folder monitoring or scanning scope settings that specify which mailbox folders are being scanned. Identify if the configuration is limited to Inbox folder tree only.Affected if The scanning configuration is set to monitor and scan messages only within the Inbox folder tree and does not include other mailbox folders.
-
Identify mailbox rules that auto-move messagesOn the Exchange Server or through mailbox auditing, review user-created rules that automatically move, forward, or redirect incoming messages to folders outside the Inbox tree or to other mailboxes.Affected if One or more mailbox rules exist that automatically move incoming messages to folders beyond the Inbox, causing those messages to bypass the Inbox-only scanning.
You are affected if Broadcom InoculateIT version 4.53 with the Exchange Server plugin is installed, configured to scan only the Inbox folder, and mailbox rules exist that route messages to other folders where they will not be scanned.
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 dataConfigure the antivirus scanning to monitor all mailbox folders beyond just Inbox, review and audit user-created mailbox rules that auto-move messages, or implement additional scanning at the gateway/server level to catch messages regardless of folder placement.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1368 — 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-1999-1368 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