CVE-2018-0607
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 · uneditedSQL injection vulnerability in the Notifications application in the Cybozu Garoon 3.5.0 to 4.6.2 allows remote authenticated attackers to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in the Notifications application of Cybozu Garoon allows remote authenticated attackers to execute arbitrary SQL commands via unspecified vectors in versions 3.5.0 through 4.6.2.
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>= 3.5.0, <= 4.6.2CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed Garoon versionAccess the Garoon administration panel and navigate to System Settings > System Information to view the current version number, or check the version file in the Garoon installation directory if you have server accessAffected if The displayed version falls between 3.5.0 and 4.6.2 inclusive
-
Confirm Notifications application is in useLog into Garoon as an administrator and verify whether the Notifications (通知) application module is installed and enabled in the system configurationAffected if The Notifications application is enabled and accessible to users
-
Review access logs for SQL injection patternsExamine Garoon access and application logs for unusual SQL syntax, quotes, or UNION statements in notification-related request parameters, particularly in the /g/ notifications API endpointsAffected if Log entries show malformed SQL-like patterns in notification-related requests
-
Check for unauthorized database modificationsQuery the Garoon database for unexpected records or modifications in notification-related tables, particularly looking for timestamps or user IDs that do not correlate with legitimate user activityAffected if Database records in notification tables contain suspicious data or were modified at unexpected times
-
Verify authentication mechanismsConfirm that all Garoon user accounts use strong authentication and that the system does not allow anonymous access to the Notifications functionalityAffected if The system allows authenticated users to access the Notifications module
You are affected if your installed Garoon version is between 3.5.0 and 4.6.2 and the Notifications application is enabled for users.
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 vendor patch (upgrade to version 4.6.3 or later); if immediate patching is not feasible, implement parameterized queries or input validation as compensating controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0607 — 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-2018-0607 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