Skip to main content
VulnerabilityPublished Updated

CVE-2024-55557: Weasis · Use of Hard-coded Credentials

Affects WeasisSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubnroduit/Weasispkg:github/nroduit/WeasisOther threatsAffected
  • =4.5.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately remove the hardcoded encryption key from the source code and replace it with a secure key management system that generates and stores keys dynamically.
  2. Implement environment-specific configuration for encryption keys rather than embedding them in code.
  3. Encrypt proxy credentials using strong, industry-standard cryptographic libraries and ensure keys are stored securely using hardware security modules (HSMs) or secure vaults.
  4. Monitor network traffic for unusual proxy authentication attempts or anomalies indicating credential misuse.
  5. Restrict network access to Weasis proxy configurations to trusted administrators only.
  6. Conduct code audits and security reviews to detect similar hardcoded secrets elsewhere in the application.
  7. Apply defense-in-depth by segmenting healthcare networks and enforcing strict access controls to limit attacker movement if credentials are compromised.
  8. Stay updated on vendor patches or advisories and apply them promptly once available.

Description

ui/pref/ProxyPrefView.java in weasis-core in Weasis 4.5.1 has a hardcoded key for symmetric encryption of proxy credentials.

References

Community reviews

Loading reviews…