Skip to content
Noroxi
CVE-2009-5057· NVD / CVE Program· CNA mitre

The S/MIME feature in Open Ticket Request System (OTRS) before 2.3.4 does not configure the RANDFILE and HOME environment variables for Open

Noroxi assessment

Priority: Monitor (action score 20/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 75.7% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: otrs2 (Debian:11) 2.4.5-1.

Low priority for now. Upgrade to otrs2 (Debian:11) 2.4.5-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

The S/MIME feature in Open Ticket Request System (OTRS) before 2.3.4 does not configure the RANDFILE and HOME environment variables for OpenSSL, which might make it easier for remote attackers to decrypt e-mail messages that had lower than intended entropy available for cryptographic operations, related to inability to write to the seeding file.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Mar 18, 2011
Updated
Jun 16, 2026
EPSS
1.6% · 76th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.6%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2009-5057

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? RSS feed for otrs records

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
otrsotrs

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • otrs otrsup to 2.3.3 inclusive
  • otrs otrs0.5
  • otrs otrs1.0
  • otrs otrs1.0.0
  • otrs otrs1.0.1
  • otrs otrs1.0.2
  • otrs otrs1.1
  • otrs otrs1.1.0
  • otrs otrs1.1.1
  • otrs otrs1.1.2
  • otrs otrs1.1.3
  • otrs otrs1.1.4
  • otrs otrs1.2.0
  • otrs otrs1.2.1
  • otrs otrs1.2.2
  • otrs otrs1.2.3
  • otrs otrs1.2.4
  • otrs otrs1.3.0
  • otrs otrs1.3.1
  • otrs otrs1.3.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11otrs2before 2.4.5-12.4.5-1

Same product

otrs: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-16921In OTRS 6.0.x up to and including 6.0.1, OTRS 5.0.x up to and including 5.0.24, and OTRS 4.0.x up to and including 4.0.26, an attacker who i
    41Plan
  • CVE-2024-23790Missing file type check in avatar picture upload
    39Monitor
  • CVE-2022-4427SQL Injection via OTRS Search API
    39Monitor
  • CVE-2026-48188SQL Injection via MySQL Quote Method
    36Monitor
  • CVE-2023-5422SSL Certificates are not checked for E-Mail Handling
    36Monitor
  • CVE-2017-17476Open Ticket Request System (OTRS) 4.0.x before 4.0.28, 5.0.x before 5.0.26, and 6.0.x before 6.0.3, when cookie support is disabled, might a
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:otrs22.4.5-1 · Debian:11Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-310 · Cryptographic Issues

CVSS vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records