Missing AuthenticationWeakness · CWE-306

CVE-2024-33622

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Missing authentication for critical function vulnerability exists in ID Link Manager and FUJITSU Software TIME CREATOR. If this vulnerability is exploited, sensitive information may be obtained and/or the information stored in the database may be altered by a remote authenticated attacker.

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

This is a missing authentication vulnerability in Fujitsu ID Link Manager and TIME CREATOR software. A critical function lacks proper authentication checks, allowing an authenticated attacker to access sensitive data or modify database contents without authorization.

MitigationImplement proper authentication and authorization checks for the vulnerable critical function to ensure only authorized users can access it.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify installed product and version
    Check the installed version of Fujitsu ID Link Manager or TIME CREATOR by reviewing the software's about dialog, installation directory readme files, or program listing in the system control panel
    Affected if The installed version falls within the affected range for this CVE (or if the version cannot be determined, assume potentially affected)
  2. Locate the software installation directory
    Find the installation folder for ID Link Manager or TIME CREATOR - typically under Program Files or a Fujitsu-specific directory - and review any configuration or executable files present
    Affected if The software is installed and running without documented authentication patches applied
  3. Identify accessible endpoints or functions
    Review the software's network configuration, API endpoints, or service interfaces to determine which functions are exposed. Check for any web service URLs, REST endpoints, or remote procedure call interfaces the software exposes
    Affected if A critical function (as described in the CVE) is accessible over the network or via an interface without requiring authentication credentials
  4. Test critical function for authentication requirement
    Attempt to access the suspected critical function endpoint without providing valid authentication credentials. Observe whether the request is rejected or accepted
    Affected if The critical function accepts and processes requests without requiring authentication, indicating the vulnerability is present
  5. Review authentication configuration settings
    Check the software's configuration files, registry entries, or security settings for any authentication-related parameters. Look for settings that control whether authentication is enforced for specific functions or modules
    Affected if Authentication enforcement is disabled, misconfigured, or missing for the critical function

The environment is affected if Fujitsu ID Link Manager or TIME CREATOR is running and the critical function described in the CVE is accessible without requiring authentication credentials.

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

Implement proper authentication and authorization checks for the vulnerable critical function to ensure only authorized users can access it.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33622 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33622 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